Apidog Tests Mcp
Let your coding agent create, organize, and maintain Apidog API test cases, scenarios, suites, and test data from the editor instead of clicking through the Apidog UI.
Overview
io.github.acabala/apidog-tests-mcp is a MCP server for the Ship phase that lets agents manage Apidog test cases, scenarios, suites, and test data over the Apidog API.
What is this MCP server?
- Manages Apidog test cases, scenarios, suites, and test data via MCP tools
- Stdio npm package @acabala/apidog-tests-mcp (v0.0.5)
- Scoped to project + branch via APIDOG_PROJECT_ID and APIDOG_BRANCH_ID
- Token auth with APIDOG_ACCESS_TOKEN against configurable Apidog API base URL
- Package version 0.0.5 on npm (@acabala/apidog-tests-mcp)
- 3 required secrets/env vars: token, project ID, branch ID
- Default API host https://api.apidog.com/api/v1 (overridable)
Community signal: 1 GitHub stars.
What problem does it solve?
Keeping Apidog tests in sync with fast-moving API code means repetitive UI work that breaks flow when you are trying to ship.
Who is it for?
Indie API builders who already use Apidog for design and tests and want MCP-driven edits during ship-week hardening.
Skip if: Teams that do not use Apidog, or builders who only need a one-off curl smoke test without a managed test catalog.
What do I get? / Deliverables
Your agent can read and update Apidog test artifacts in-repo context so suites stay current as endpoints and branches change.
- Agent-callable tools to manage Apidog test cases and suites
- Branch-scoped test data operations aligned to your Apidog project
Recommended MCP Servers
Journey fit
API test design and suite management sit squarely in the ship phase when you are hardening integrations before release. Test cases, scenarios, and suites are classic automated testing artifacts, not launch SEO or production monitoring.
How it compares
Apidog API bridge via MCP, not a standalone test framework or OpenAPI linter skill.
Common Questions / FAQ
Who is io.github.acabala/apidog-tests-mcp for?
Solo and small-team developers who standardize API testing in Apidog and use Claude Code, Cursor, or Codex with MCP stdio servers.
When should I use io.github.acabala/apidog-tests-mcp?
Use it during ship and testing when you are updating endpoints, branches, or regression suites and want the agent to sync Apidog cases and data without manual UI edits.
How do I add io.github.acabala/apidog-tests-mcp to my agent?
Install @acabala/apidog-tests-mcp from npm, set APIDOG_ACCESS_TOKEN, APIDOG_PROJECT_ID, and APIDOG_BRANCH_ID, wire stdio transport in your MCP config, then restart the client.