API Testing MCP Server

1

Add it to Claude Code

Run this in a terminal.

Run in terminal
claude mcp add api-testing-mcp -- npx -y @cocaxcode/api-testing-mcp@latest
README.md

The most complete MCP server for API testing.

@cocaxcode/api-testing-mcp

<strong>The most complete MCP server for API testing. Period.</strong>
35 MCP tools &middot; Zero config &middot; Works in any MCP client

Overview · Just Talk to It · Installation · Features · Tool Reference · Storage · Architecture


Quick Overview

The most complete MCP server for API testing — 35 tools, zero config, nothing else comes close. This is not just a request sender. It is a full testing workbench: HTTP requests with assertions, multi-step flows with variable extraction, OpenAPI import with schema-aware mock data, load testing with percentile metrics, response diffing across environments, bulk test runners, reusable collections, project-scoped environments, Postman import/export, and cURL export. All from natural conversation. No accounts, no cloud, no generated files. Everything runs inline and stores as plain JSON you own.


Just Talk to It

You don't need to learn tool names or parameters. Describe what you want and the AI picks the right tool.

"Set up an environment called dev with BASE_URL http://localhost:3000"
"Import my API spec from /api-docs-json"
"Show me all user endpoints"
"GET /users"
"Create a user with random data"
"Verify that DELETE /users/5 returns 204"
"Login as admin, extract the token, then fetch dashboard stats"
"How fast is /health with 50 concurrent requests?"
"Run all my saved smoke tests"
"Compare the users endpoint between dev and prod"
"Export the create-user request as curl"
"Export my collection to Postman"

If you've imported an OpenAPI spec, the AI already knows every endpoint, every required field, every valid enum value. When you say "create a blog post", it reads the schema and builds the request correctly — no guessing.


Installation

Claude Code

claude mcp add --scope user api-testing -- npx -y @cocaxcode/api-testing-mcp@latest

Claude Desktop

Add to your config file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):

{
  "mcpServers": {
    "api-testing": {
      "command": "npx",
      "args": ["-y", "@cocaxcode/api-testing-mcp@latest"]
    }
  }
}

Cursor / Windsurf

Add to .cursor/mcp.json or .windsurf/mcp.json in your project root:

{
  "mcpServers": {
    "api-testing": {
      "command": "npx",
      "args": ["-y", "@cocaxcode/api-testing-mcp@latest"]
    }
  }
}
VS Code / Codex CLI / Gemini CLI

VS Code — add to .vscode/mcp.json:

{
  "servers": {
    "api-testing": {
      "command": "npx",
      "args": ["-y", "@cocaxcode/api-testing-mcp@latest"]
    }
  }
}

Codex CLI (OpenAI):

codex mcp add api-testing -- npx -y @cocaxcode/api-testing-mcp@latest

Or add to ~/.codex/config.toml:

[mcp_servers.api-testing]
command = "npx"
args = ["-y", "@cocaxcode/api-testing-mcp@latest"]

Gemini CLI — add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "api-testing": {
      "command": "npx",
      "args": ["-y", "@cocaxcode/api-testing-mcp@latest"]
    }
  }
}

Quick Start

Once installed, set up an environment so relative paths resolve automatically:

"Create an environment called dev with BASE_URL http://localhost:3000"

If your API has a Swagger/OpenAPI spec, import it:

"Import my API spec from http://localhost:3000/api-docs-json"

Verify with: "List my environments" — you should see the one you just created.


Features

HTTP Requests

Send any HTTP method with headers, query params, JSON body, auth, and {{variable}} interpolation. Relative URLs auto-resolve again

Configuration

claude_desktop_config.json
{"mcpServers": {"api-testing": {"command": "npx", "args": ["-y", "@cocaxcode/api-testing-mcp@latest"]}}}

Try it

Import my API spec from http://localhost:3000/api-docs-json
Create an environment called dev with BASE_URL http://localhost:3000
Verify that DELETE /users/5 returns 204
How fast is /health with 50 concurrent requests?
Export my collection to Postman

Frequently Asked Questions

What are the key features of API Testing MCP?

HTTP request execution with assertions and variable extraction. OpenAPI specification import with schema-aware mock data generation. Load testing with percentile metrics. Response diffing across different environments. Bulk test runners and reusable API collections.

What can I use API Testing MCP for?

Automating API smoke tests within an AI-assisted development workflow. Validating API endpoints against OpenAPI schemas without manual configuration. Performing load testing on local development servers. Comparing API responses between development and production environments. Exporting API test collections to Postman for team collaboration.

How do I install API Testing MCP?

Install API Testing MCP by running: claude mcp add --scope user api-testing -- npx -y @cocaxcode/api-testing-mcp@latest

What MCP clients work with API Testing MCP?

API Testing MCP works with any MCP-compatible client including Claude Desktop, Claude Code, Cursor, and other editors with MCP support.

Turn this server into reusable context

Keep API Testing MCP docs, env vars, and workflow notes in Conare so your agent carries them across sessions.

Need the old visual installer? Open Conare IDE.
Open Conare