MCP server for managing Apidog test cases, scenarios, suites, and test data, providing AI assistants with full read/write access to Apidog's test management features.
From the registry: MCP server for managing Apidog test cases, scenarios, suites, and test data
Please install the `apidog-tests-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Get Apidog access token** — Obtain an Apidog access token and identify your project ID and branch ID
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["@acabala/apidog-tests-mcp"]
- required environment variables:
- `APIDOG_ACCESS_TOKEN`: Your Apidog access token (example: `<your-token>`)
- `APIDOG_PROJECT_ID`: The Apidog project ID (example: `<your-project-id>`)
- `APIDOG_BRANCH_ID`: The branch ID to work with (example: `<your-branch-id>`)
- optional environment variables:
- `APIDOG_BASE_URL`: Override the API base URL (example: `https://api.apidog.com/api/v1`)
Note: Unofficial Apidog integration. Full CRUD for test cases, scenarios, suites, and test data.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.APIDOG_ACCESS_TOKENrequiredYour Apidog access tokenAPIDOG_PROJECT_IDrequiredThe Apidog project IDAPIDOG_BRANCH_IDrequiredThe branch ID to work withReal-time Kubernetes network traffic visibility and API analysis for HTTP, gRPC, Redis, Kafka, DNS.