01
Your spec is the source
Every operation in your OpenAPI document becomes an MCP tool. Its input schema is built from the operation's parameters and request body, so you don't hand-write tool definitions.
OpenAPI → MCP, hosted for you
Ship an official MCP server for your API on your domain.
Point SpecSync at your OpenAPI spec and choose which endpoints AI agents can call. SpecSync serves them as a hosted MCP server at mcp.yourcompany.com. There's nothing to deploy, and every call is metered per tool.
Works with Claude, Cursor, VS Code and other MCP clients.
Example bridge · Orders APIIllustration
| REST operation | MCP tool | |
|---|---|---|
| GET /v1/orders | list_orders(called this cycle) | |
| GET /v1/orders/{id} | get_order(called this cycle) | |
| POST /v1/orders | create_order(called this cycle) | |
| GET /v1/customers/{id} | get_customer(idle this cycle) | |
| POST /v1/refunds | create_refund(called this cycle) |
Endpoint
mcp.yourcompany.com
Tools
5 exposed
Transport
HTTP + SSE
Why SpecSync
An MCP server that's officially yours
Your customers' agents want to use your API. SpecSync gives them a supported way in, built from the spec you already maintain.
02
Served on your domain
Point a CNAME such as mcp.yourcompany.com at SpecSync and TLS is issued automatically. Agents connect to a server under your name, not ours.
03
You choose what agents can reach
Expose only the operations you pick. Keep admin, billing and destructive endpoints unpatched.
04
Metered per tool
Every call is counted for each tool, each bridge and each billing cycle, so you can see which capabilities agents actually use.
05
Auth stays with the caller
Auth headers the client sends (Authorization, x-api-key and X- headers) are forwarded to your API. SpecSync never stores your credentials.
06
Nothing to run
There's no MCP server process, container or SDK upgrade on your side. SpecSync hosts the endpoint and proxies each call to your API.
How it works
From spec to live server in three steps
- Step 1 · Spec in
Point at your OpenAPI spec
Use a public URL or paste the JSON. OpenAPI 3.0, 3.1 and Swagger 2.0 are supported.
https://api.yourcompany.com/openapi.json - Step 2 · Patch
Choose the tools
Each operation becomes a named tool. Turn off anything agents shouldn't touch.
POST /v1/refunds → create_refund - Step 3 · Serve
Hand out one URL
Add it to Claude, Cursor, VS Code or your docs. Put it on your own domain whenever you're ready.
https://mcp.yourcompany.com
Pricing
Priced on tool calls
Every plan gets the full product. Plans differ in how many bridges you can run and how many tool calls they carry each month.
Every plan includes
- Custom domain with automatic TLS
- Choose which tools to expose
- Per-tool usage metering
FAQ
Common questions
See the full FAQ for limits, specs and local APIs.
What is an MCP server?
The Model Context Protocol (MCP) is an open standard that lets AI clients such as Claude, Cursor and VS Code discover and call external tools. An MCP server publishes a list of tools with typed inputs and runs them when an agent calls them. SpecSync hosts that server for your API.
How do I turn my OpenAPI spec into an MCP server?
Give SpecSync the URL of your OpenAPI document, or paste the JSON. Each operation becomes an MCP tool whose input schema comes from its parameters and request body. You pick which tools to expose, and SpecSync gives you a hosted MCP endpoint you can add to any MCP client.
Can the MCP server run on my own domain?
Yes. Add a CNAME record pointing a hostname such as mcp.yourcompany.com at mcp.specsync.io, then verify it in the dashboard. SpecSync issues TLS automatically, and clients connect to your hostname.
How does authentication to my API work?
SpecSync doesn't ask for or store your API's credentials. The MCP client sends its own auth headers (Authorization, x-api-key or any X- header), and SpecSync forwards them to your API on each tool call.
Which spec formats are supported?
OpenAPI 3.0 and 3.1, plus Swagger 2.0, in JSON. If your spec is YAML, convert it to JSON first.
Which MCP clients can connect?
Any client that supports MCP over HTTP with Server-Sent Events. That includes Claude Code, Cursor and VS Code. Claude Desktop connects through the mcp-remote adapter.
Your API is already built. Patch it in.
Connects to
- Claude Code
- Claude Desktop
- Cursor
- VS Code
- Any MCP client (HTTP + SSE)