Rest Api to Mcp Wrapper
Turn any REST API into MCP tools automatically — feed it an OpenAPI spec or endpoint list, get a working MCP server with clean tool schemas.
$12
Works with the AI Agents you already use
About this skill
Your agent needs to talk to a REST API. Writing the MCP server by hand means translating every endpoint into a tool definition, getting the schemas right, handling pagination, and mapping errors — hours of careful, boring work per API. This skill automates it: give it an OpenAPI/Swagger spec (or even a plain endpoint list), and it generates a complete MCP server with one tool per endpoint, sensible input schemas derived from the spec, pagination helpers, and error mapping — plus a review pass that fixes the things generators always get wrong.
To convert a REST API contract into a working MCP server with minimal human effort: parse the spec, generate one well-described tool per operation, derive strict JSON schemas from request bodies and parameters, add pagination and auth wiring, and produce the same production hygiene as a hand-built server (structured errors, logging, tests). The human's job shrinks to reviewing the generated tool descriptions and approving the auth mapping.
-
When you want your agent to use a third-party REST API (Stripe-style, internal platform API, SaaS API) and an OpenAPI spec exists.
-
When the spec is missing but you have docs or an endpoint list — the skill works from those too, marking generated schemas as
assumedwhere it had to guess. -
When you need to wrap several related APIs and want consistent tool naming and error shapes across all of them.
-
When an API adds new endpoints and you need to regenerate without losing your hand-written customizations (the skill uses clearly-marked
GENERATEDvsCUSTOMregions). -
When the API is GraphQL, gRPC, or event-driven — the generation heuristics are REST/HTTP-specific and will produce nonsense.
-
When you are designing an API from scratch — use
mcp-server-scaffolderfor greenfield tool design; this skill wraps what already exists. -
When the spec is so broken it cannot be parsed (the skill will tell you, and suggest fixing the spec first — possibly with
api-contract-reviewer). -
For APIs requiring complex multi-step workflows per tool (e.g. "create order" needs 4 calls with state) — generated tools are one-call-per-tool; orchestration belongs in the agent, or hand-write those tools.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 29 days ago
Requires
Permissions
Allowed Hosts