mcpify
mcpify
Turn any REST API into an MCP server in one command. Point mcpify at an OpenAPI
spec and every endpoint becomes a tool your AI agent (Claude, Cursor, Windsurf, …) can
call — no glue code, no per-endpoint wrappers.
mcpify https://api.example.com/openapi.jsonThat's it. Every operation in the spec is now a live MCP tool.
Why
MCP is how AI agents call real tools. But wiring an
existing API into MCP means hand-writing a tool wrapper for every endpoint — tedious and
stale the moment the API changes. Almost every API already publishes an OpenAPI spec.
mcpify reads that spec and generates the whole MCP server at runtime, so:
Zero per-endpoint code — N endpoints → N tools, automatically.
Always in sync — regenerate from the spec; no wrappers to maintain.
Auth-aware — pass an API key / bearer token once, applied to every call.
Related MCP server: APIFold
Install
pipx install mcpify-cli # or: uvx mcpify-cli ...Use
Preview the tools a spec produces (no server):
mcpify --list examples/petstore-mini.yamlRun it as an MCP server (stdio):
mcpify https://petstore3.swagger.io/api/v3/openapi.json
mcpify ./openapi.yaml --base-url https://staging.internal.api
mcpify ./openapi.yaml --auth "Authorization: Bearer $TOKEN" # or set MCPIFY_AUTHPlug it into Claude
Add to your MCP client config (Claude Desktop / Claude Code mcp.json):
{
"mcpServers": {
"petstore": {
"command": "mcpify",
"args": ["https://petstore3.swagger.io/api/v3/openapi.json"]
}
}
}Restart the client and ask: "list the available pets" — Claude calls the API directly.
How it works
Load the OpenAPI 3.x document (URL or file, JSON or YAML).
Walk every path/method into an
Operationwith a generated JSON input schema.Serve them over MCP; each tool call is mapped to a live HTTP request (path, query, header params and JSON bodies all handled) and the response is returned to the agent.
Supported
OpenAPI 3.x, JSON or YAML, from a URL or local file
GET/POST/PUT/PATCH/DELETEPath, query, and header parameters; JSON request bodies
A single global auth header (API key or bearer token)
Roadmap
Per-operation filtering (
--only,--tag) to expose a subset of a large API$refresolution for fully-expanded body schemasSwagger 2.0 specs
SSE / HTTP transport in addition to stdio
PRs welcome.
License
MIT
Available Tools
3 toolsTool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a distinct purpose: create, get by ID, and list all pets. No ambiguity or overlap.
All tools follow a consistent camelCase verb_noun pattern: createPet, getPet, listPets.
Three tools is appropriate for a basic pet management scope, though slightly minimal.
Domain is pet management; missing update and delete operations are notable gaps for full lifecycle.
Maintenance
Related MCP Connectors
Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
One MCP endpoint for Claude, GPT & Gemini: 100+ tools + no-code connectors + agent workers.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceAutomatically converts Swagger/OpenAPI specifications into MCP servers, enabling AI agents to interact with any REST API through natural language by exposing endpoints as AI-friendly tools.3-
- AlicenseAqualityDmaintenanceTurn any REST API into a hosted MCP server. 18 free public servers (GitHub, Stripe, Slack, OpenAI, Notion, and more) — no setup required, bring your own API key.213AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceTurns any OpenAPI specification into a fully working MCP server with a single command, enabling AI agents to call APIs without writing any glue code.MIT
- AlicenseNot gradedqualityDmaintenanceTurns any OpenAPI REST or GraphQL API into an MCP server, allowing AI assistants like Claude to interact with APIs without writing code.16 npmMIT