Api Testing Mcp
Let your coding agent run HTTP calls, assertions, multi-step API flows, OpenAPI checks, and saved collections without leaving the chat.
Overview
io.github.cocaxcode/api-testing-mcp is a MCP server for the Ship phase that gives agents 35 tools to execute HTTP requests, assertions, flows, OpenAPI checks, and API test collections.
What is this MCP server?
- 35 MCP tools covering HTTP requests, response assertions, chained flows, OpenAPI validation, and test collections
- stdio transport via npm package @cocaxcode/api-testing-mcp (v0.11.5)
- Supports building repeatable API smoke and contract checks from agent-driven sessions
- OpenAPI-aware workflows for aligning requests with documented contracts
- Collection-oriented runs for multi-endpoint scenarios indie APIs need
- 35 MCP tools (HTTP, assertions, flows, OpenAPI, collections)
- Package @cocaxcode/api-testing-mcp v0.11.5
- stdio transport via npm registry
Community signal: 2 GitHub stars.
What problem does it solve?
Solo builders waste cycles flipping between the IDE, terminal curl, and Postman when an agent could run structured API checks on demand.
Who is it for?
Indie devs shipping REST or webhook-backed SaaS who want agent-assisted smoke tests, contract checks, and flow debugging before release.
Skip if: Teams that only need browser E2E UI tests with no API surface, or orgs that forbid agents from hitting networked staging endpoints.
What do I get? / Deliverables
After you register the server, your agent can drive repeatable HTTP and assertion workflows against your API from one stdio MCP connection.
- Agent-executable HTTP requests and response assertions against your API
- Multi-step flow runs and collection-based regression checks
- OpenAPI-aligned validation feedback the agent can iterate on in code
Recommended MCP Servers
Journey fit
API verification belongs on the Ship shelf because it is how solo builders prove backends and integrations work before launch. Testing is the canonical subphase for exercising endpoints, schemas, and regression flows against real or staging APIs.
How it compares
MCP API test harness with 35 tools, not a browser automation skill or a hosted CI-only runner.
Common Questions / FAQ
Who is io.github.cocaxcode/api-testing-mcp for?
It is for solo and small-team builders using AI coding agents who need to test HTTP APIs, assertions, and multi-step flows from Claude Code, Cursor, or Codex.
When should I use io.github.cocaxcode/api-testing-mcp?
Use it in Ship when you are validating endpoints, OpenAPI contracts, or regression collections before you tag a release or promote to production.
How do I add io.github.cocaxcode/api-testing-mcp to my agent?
Install @cocaxcode/api-testing-mcp from npm, add an MCP server entry with stdio transport pointing at that package, and restart your agent host so the 35 tools load.