ProxyPI
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ProxyPI POST https://api.example.com/users {"name":"John"}"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.

What it is
Self-healing API proxy MCP for Cursor, Claude Code, or any MCP-compatible client. Send any REST request — if it fails, ProxyPI reads the error, diagnoses the problem using Claude, patches the request, and retries. Successful fixes are remembered and applied instantly next time, without calling Claude.
Related MCP server: qa-probe
How it works
You: proxypi_request → POST https://api.example.com/users
ProxyPI: try → fail → diagnose (Claude) → patch → retry → rememberNext time the same error occurs on the same host and path, the fix is applied from memory instantly — no Claude call needed.
Demo
npx proxypiInstall
npx proxypiConfig
Add to .cursor/mcp.json (project root or ~/.cursor/mcp.json):
{
"mcpServers": {
"proxypi": {
"command": "npx",
"args": ["-y", "proxypi"],
"env": {
"ANTHROPIC_API_KEY": "your-api-key-here"
}
}
}
}Restart Cursor. Four tools: proxypi_request, proxypi_history, proxypi_replay, proxypi_clear.
Tools
Tool | Description |
| Send any REST request — auto-heals on failure |
| View past fixes, filter by API host |
| Re-run a stored fix to verify it still works |
| Wipe all healing records from memory |
What ProxyPI can fix
Error | What ProxyPI does |
| Fixes Authorization header format (Bearer vs Basic vs token prefix) |
| Fixes body field names, types, or missing required fields |
| Corrects schema mismatches, enum values, date formats |
| Fixes URL path, API version prefix, trailing slashes |
| Switches to the correct HTTP method |
More
Memory: Fixes stored in
~/.proxypi/memory.jsonEnv:
ANTHROPIC_API_KEYrequired (only when using healing — server starts without it)Local dev:
cp .env.example .env, add key, thennpm run devTests:
npm test
MIT · GitHub
Available Tools
4 toolsproxypi_clearA
Clear all stored healing records from memory.
Inputs: no named parameters.
proxypi_historyA
Show the history of auto-healed API requests. Optionally filter by API host.
Inputs: host, limit.
proxypi_replayB
Replay a previously healed request. Useful for testing that a fix still works after an API update.
Inputs: host (required), index.
proxypi_requestA
Send a request to any REST API. If the request fails, ProxyPI diagnoses the error, patches the request using Claude, and retries automatically — up to 3 times. Learned fixes are remembered and applied instantly next time without calling Claude.
Examples:
POST https://api.stripe.com/v1/customers with a body
Any REST endpoint with headers, body, or query params
Inputs: url (required), body, method, params, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: send a request, view history, replay a healed request, and clear records. No overlap or ambiguity between them.
All tool names follow the consistent pattern 'proxypi_' prefix plus a simple action verb (request, history, replay, clear), using lowercase snake_case throughout.
With 4 tools, the set is compact and well-scoped for a proxy request healer. Each tool earns its place without redundancy or bloat.
The tool surface fully covers the request-healing lifecycle: sending, reviewing history, replaying, and clearing records. There are no obvious dead ends or missing operations for the stated domain.
Maintenance
Related MCP Connectors
MCP diagnostics that help AI agents find safe next steps for HTTP, API, and MCP failures.
Free MCP debugging tools for AI agents and developers. Diagnose failed API and MCP tool calls, identify HTTP errors, validate tool arguments against supported JSON Schema rules, and get actionable troubleshooting recommendations.
AI-native mock API server with MCP. Create REST/SOAP mocks from Claude, Cursor, or Windsurf.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Related MCP Servers
- AlicenseAqualityDmaintenanceSelf-healing proxy for MCP servers that wraps tool calls with automatic retry, circuit breaker protection, and observability.557 npmMIT

qa-probeofficial
AlicenseAqualityBmaintenanceProbes your live API and classifies why each endpoint failed (root cause, evidence, and a calibrated confidence level), exposed over MCP so your AI assistant debugs from evidence instead of guessing. Works with FastAPI, Express, Next.js, tRPC, and GraphQL.8366 npm2Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnables testing and interacting with any REST API endpoint directly from MCP clients like Claude and Cline. Supports GET, POST, PUT, DELETE, and PATCH requests with configurable authentication (Basic, Bearer, API Key), custom headers, SSL verification control, and response size limits.5 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables testing and interacting with any REST API endpoints directly from MCP clients such as Claude and Cline, supporting GET, POST, PUT, DELETE, and PATCH requests with detailed status, header, and body responses. It handles Basic, Bearer, and API Key authentication, custom headers, configurable SSL verification, and response size limits.5 npmISC