Anyone can proxy REST to MCP. What breaks in practice is editing a live tool definition and discovering that production agents changed behaviour mid-conversation. Keeping production on immutable published versions while edits land in a draft — and giving agents a separate editor endpoint to work on the draft — is the difference between a demo and something you can operate. The per-call price on the pay-as-you-go plan makes the cost of an agent's retry loop visible, which is worth knowing before you turn one loose.
A platform for wrapping your own REST API as an MCP server. Each tool maps one-to-one to an endpoint — get_weather calls GET /api/weather — with authentication, headers and body configured per tool. The endpoint address is per customer, so there is no shared URL to connect to.
- Tool definitions mapped to your endpoints, with templated headers passed automatically on every call
- Optional MCP Prompts for clients that expect reusable presets
- Dev and prod environments with immutable published versions alongside a workspace draft
- An editor endpoint so an agent in Cursor can compare published against draft, edit draft tools, and save or publish a version
- Tool tracing and audit trails over the calls agents make
An account and your own API. Stream is the recommended transport, SSE the alternative; clients without remote support go through mcp-remote with the headers passed as flags. A self-hosted edition runs on your own VM under Docker Compose for data residency.
Paste a URL with a key — add the endpoint to your client