Point our MCP at your codebase and it reads your routes, proposes the tools an agent should see, and stands up a live MCP server — behind keys, access scopes and rate limits. No gateway to hand-build, no manifest to hand-write. Prefer a spec? Import your OpenAPI and you're live in minutes either way.
/mcp/s/<slug>/Wrapping each route as an agent tool — schemas, auth, descriptions — is fiddly, repetitive work that goes stale the moment the API changes.
With no clear description of what each endpoint returns, an agent can't reliably decide which one to call — or what to do with the response.
Opening an API to agents means keys, scopes, rate limits and quotas. Standing that gateway up is its own project.
Most tools make you describe every endpoint by hand, then drift from the real API. Make Me An MCP has its own MCP. You connect it inside Claude, Cursor or Codex and ask it to set up your server. It reads your routes and OpenAPI, proposes the capability groups and when-to-use hints, and scaffolds a live server you confirm — so the manifest agents read is generated from your actual code, not copy-pasted prose.
Connect Make Me An MCP in your agent and ask it to set up your server. It reads your routes, proposes the tools, and scaffolds a live MCP — guided end to end.
Already have a spec? Paste or link your OpenAPI/Swagger and every path becomes a grouped, agent-ready tool automatically.
It reads the shape of each endpoint's response so the manifest tells agents exactly what comes back — not just what to send.
An auto-drafted manifest you can edit — the description agents read to choose which API to invoke, and why.
Internal, enterprise, or private. Every consumer connects with a key scoped to what it's allowed to touch, with recommended rate limits and quotas set for you.
Every call is metered per key and endpoint, with rate-limit and quota hits tracked — so you can see exactly what agents are doing with your API.
It's a free alpha right now. Join in, build your MCP, and help us shape the product — and its pricing — before we set any. Your feedback is the point.
Make Me An MCP has its own MCP. Connect it in Claude, Cursor or Codex and ask it to set up your server. It reads your routes and OpenAPI, proposes the tools and groups, and scaffolds a live server you confirm.
No. It builds the agent-facing surface on top of the API you already run — reading each endpoint's output signature and generating the manifest for you.
Every consumer connects with a key scoped to what it's allowed to touch. You decide whether a server is internal, enterprise, or private, with recommended rate limits and quotas set for you.
They read the manifest — the auto-drafted, editable "yellow pages" describing each group and endpoint, when to use it, and the shape of what it returns.
Join the free alpha
Tell us about your API and we'll get you set up — the code-reading MCP, the import, the controls. In return, we want your honest feedback while we build this with you.