Apidog Tests MCP Server

Connect Apidog Tests MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for managing Apidog test cases, scenarios, suites, and test data. The apidog tests mcp mcp server is what makes that connection.

What the server does

MCP (Model Context Protocol) server for managing Apidog test cases, scenarios, suites, and test data. Gives AI assistants full read/write access to Apidog's test management features.

• Test Cases — -- Create, read, update, delete, and bulk-create test cases for API endpoints
• Test Scenarios — -- Build multi-step test flows chaining multiple API calls
• Test Suites — -- Organize tests into runnable suites for CI/CD
• Test Data — -- Manage data-driven test iterations with CSV-formatted data
• Folders — -- Organize scenarios and suites into nested folder structures
• Read-only tools — -- List environments, endpoints, categories, tags, runners, and coverage statistics

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Folders — The Folders tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: APIDOG_ACCESS_TOKEN, APIDOG_PROJECT_ID, APIDOG_BRANCH_ID, APIDOG_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Apidog Tests MCP's toolset — Folders — is a fair guide to whether it matches your workflow. It is maintained by acabala; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Apidog Tests MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.