API Testing MCP server

by cocaxcode·io.github.cocaxcode/api-testing-mcp·v0.11.12·9 stars

No reviews yet

MCP server for API testing. 35 tools: HTTP, assertions, flows, OpenAPI, collections.

B78/100grade B

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

B78/100

full report

Adoption

Growing

9 stars86 downloads/wk

Reviews

Write one

Nobody has reviewed API Testing yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

API Testing tools (34, 4 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

api_endpoint_detail
Muestra el detalle completo de un endpoint: par\xE1metros, body schema, y respuestas. \xDAtil para saber qu\xE9 datos enviar.
api_endpoints
Lista los endpoints de un API importada. Filtra por tag, m\xE9todo o path. Si no se especifica nombre y solo hay un spec importado, lo usa autom\xE1ticamente.
api_import
Importa un spec OpenAPI/Swagger desde una URL o archivo local (JSON o YAML). Guarda los endpoints y schemas para consulta.
api_spec_list
Lista todos los specs de API importados. \xDAsalo para descubrir qu\xE9 APIs est\xE1n disponibles.
assert
Ejecuta un request y valida la respuesta con assertions. Retorna resultado pass/fail por cada assertion.
bulk_test
Ejecuta todos los requests guardados en la colecci\xF3n y reporta resultados. Filtrable por tag.
collection_deletewrite action
Elimina un request guardado de la colecci\xF3n.
collection_get
Obtiene los detalles completos de un request guardado por su nombre.
collection_list
Lista todos los requests guardados en la colecci\xF3n. Opcionalmente filtra por tag.
collection_save
Guarda un request en la colecci\xF3n local. Si ya existe un request con el mismo nombre, lo sobreescribe.
diff_responses
Ejecuta dos requests y compara sus respuestas. \xDAtil para detectar regresiones o comparar entornos.
env_createwrite action
Crea un nuevo entorno (ej: dev, staging, prod) con variables opcionales.
env_deletewrite action
Elimina un entorno y todas sus variables. Si es el entorno activo, lo desactiva.
env_get
Obtiene una variable espec\xEDfica o todas las variables de un entorno.
env_list
Lista todos los entornos disponibles e indica cu\xE1l est\xE1 activo.
env_project_clear
Elimina la asociaci\xF3n de entorno espec\xEDfico de un proyecto. El proyecto usar\xE1 el entorno global.
env_project_list
Lista todos los proyectos con entornos espec\xEDficos asignados.
env_rename
Renombra un entorno existente. Si es el entorno activo, actualiza la referencia.
env_set
Establece una variable en un entorno. Si no se especifica entorno, usa el activo.
env_spec
Asocia o desasocia un spec API a un entorno. Si no se especifica entorno, usa el activo.
env_switch
Cambia el entorno activo. Si se especifica project, solo aplica a ese directorio de proyecto.
export_collection
Exporta los requests guardados en formato nativo (JSON) a .atm/. Carpeta portable \u2014 c\xF3piala a otro proyecto para importar.
export_curl
Genera un comando cURL a partir de un request guardado en la colecci\xF3n. Listo para copiar y pegar.
export_environment
Exporta un entorno en formato nativo (JSON) a .atm/. Carpeta portable \u2014 c\xF3piala a otro proyecto para importar.
export_postman_collection
Exporta los requests guardados como una Postman Collection v2.1 (JSON). Escribe el archivo en disco, importable directamente en Postman.
export_postman_environment
Exporta un entorno como Postman Environment (JSON). Escribe el archivo en disco, importable directamente en Postman.
flow_runwrite action
Ejecuta una secuencia de requests en orden. Extrae variables de cada respuesta para usar en pasos siguientes con {{variable}}.
import_collection
Importa requests desde .atm/collection.json o un archivo espec\xEDfico. Auto-detecta .atm/ en el proyecto.
import_environment
Importa un entorno desde .atm/ o un archivo espec\xEDfico. Auto-detecta archivos .env.json en .atm/.
import_postman_collection
Importa una Postman Collection v2.1 (JSON) como requests guardados en la colecci\xF3n. Soporta folders, auth, headers, body y query params.
import_postman_environment
Importa un Postman Environment (JSON) como entorno local. Soporta variables con valores initial/current.
load_test
Lanza N requests concurrentes al mismo endpoint y mide tiempos promedio, percentiles y tasa de errores.
mock
Genera datos mock/fake para un endpoint bas\xE1ndose en su spec OpenAPI importada. \xDAtil para frontend sin backend.
request
Ejecuta un HTTP request. URLs relativas (/path) usan BASE_URL del entorno activo. Soporta {{variables}}.

Public scan report

scanner v0.1.10 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings

Code scan3 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 148 days ago8/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How API Testing compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 78/100; higher than 57% of 48,273 servers
Tools: 34; the typical server has 7
Tools that change things: 12%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 9; more than 87% of 28,534 servers
Downloads a week: 86; more than 61% of 11,915 servers with a package

What its tools let an agent do: 26 read · 4 create · 4 change

Install API Testing in Claude Code, Cursor or VS Code

Runs npx -y @cocaxcode/api-testing-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add api-testing-mcp -- npx -y @cocaxcode/api-testing-mcp

Add to Cursor

What the publisher says

From the API Testing repository's README, as published. We do not edit it. Read it on GitHub

@cocaxcode/api-testing-mcp The most complete MCP server for API testing. Period. 42 MCP tools · Zero config · 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 — 42 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, environment groups with directory scoping and persistent defaults, 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.

"Create a group called my-project and add this directory as scope"
"Set up a dev environment with BASE_URL http://localhost:3000"
"Switch to prod for this session"
"Set dev as the default environment"
"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/claudedesktopconfig.json on macOS, %APPDATA%\Claude\claudedesktopconfig.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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

API Testing: common questions

Is API Testing MCP server safe?: Mostly: it is graded B (78/100). Read the API Testing safety report
How do I install API Testing?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does API Testing need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is API Testing maintained?: The last commit was 184 days ago (2026-05-02). The latest release is v0.11.12.
What can I use instead of API Testing?: Servers from other publishers that do the same job: Keploy MCP server.
How does API Testing compare with other MCP servers?: safety score 78/100 (higher than 57% of 48,273 servers); tools 34 (the typical server has 7); tools that change things 12% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to API Testing

Same job from other publishers: the closest match first, then the best rated.

Keploy
End-to-end API testing — generate and run tests from OpenAPI, curl, Postman, or real user traffic.
not reviewed
Established
A