Coverage goes past creating cases: scenarios chain endpoints into a flow, suites group them for CI, and test data arrives as CSV so one case runs across many rows. The update tools read the current state and merge, which matters because the underlying API replaces wholesale — passing one field would otherwise drop everything else. Deletions of cases, scenarios and suites cannot be undone.
A server over Apidog's test management: test cases against endpoints, scenarios that chain several calls, suites for CI, and the CSV-driven data behind data-driven runs. It is an independent project, not an official Apidog integration.
- The endpoint tree with IDs, names and folder structure — which is where the apiDetailId a test case needs comes from
- Test cases listed and filtered by endpoint, opened in full with their parameters, request body and assertions, created singly or in bulk, and deleted
- Updates that fetch the current state and merge your changes, so passing only the fields you want changed does not wipe the rest
- Test scenarios — multi-step flows — created, their steps read with the full request detail per step, and their steps replaced as a complete set
- Test suites for CI grouping, created and read in full, with their items set as groups of test cases or scenarios
- Folders for organizing scenarios and suites, nestable through a parent
- Data-driven test data: records listed for a case, read with their CSV rows and column definitions, created from CSV where the first line is the header, updated by merge, and deleted
- The supporting lookups — environments with their base URLs, test case categories and tags, the self-hosted runners available, and endpoint test-coverage statistics
An Apidog account and three settings, all required: APIDOG_ACCESS_TOKEN, APIDOG_PROJECT_ID and APIDOG_BRANCH_ID — the token scopes what you can reach, and the project and branch decide where the tests land. APIDOG_BASE_URL overrides the API base, which defaults to https://api.apidog.com/api/v1. Run it with npx @acabala/apidog-tests-mcp over stdio, from the npm package @acabala/apidog-tests-mcp, currently 0.0.6. For a case to actually execute rather than hit the bare base URL, the create call needs the endpoint path, a parameters.path entry for each route placeholder, a working auth configuration and a valid responseId.
One command plus a key — npx @acabala/apidog-tests-mcp, then supply credentials