Guide
Connect Claude to your API
Turn your OpenAPI spec into an MCP server with SpecSync, then add it to Claude Desktop or Claude Code. It takes about two minutes once you have a bridge.
Before you start
- A SpecSync bridge. Create one from your OpenAPI spec in the dashboard.
- The bridge's MCP endpoint URL, shown on its bridge page. It looks like
https://mcp.specsync.io/…, or your own hostname if you've added a custom domain. - For Claude Desktop: Node.js, so
npxcan run themcp-remoteadapter.
Claude Desktop
Open Settings → Developer → Edit Config and add your bridge to claude_desktop_config.json:
claude_desktop_config.json
{
"mcpServers": {
"my-api": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.specsync.io/YOUR-BRIDGE-ID"]
}
}
}Restart Claude Desktop. Your API's operations show up as tools in the tools menu.
Claude Code
Run this in your terminal:
terminal
claude mcp add --transport sse my-api https://mcp.specsync.io/YOUR-BRIDGE-IDPassing your API key
SpecSync doesn't store your API's credentials. It forwards the Authorization, x-api-key and other X- headers the client sends. Set the header in the client:
claude_desktop_config.json
{
"mcpServers": {
"my-api": {
"command": "npx",
"args": [
"-y", "mcp-remote", "https://mcp.specsync.io/YOUR-BRIDGE-ID",
"--header", "x-api-key:${API_KEY}"
],
"env": { "API_KEY": "your-api-key" }
}
}
}terminal
claude mcp add --transport sse my-api https://mcp.specsync.io/YOUR-BRIDGE-ID \
--header "x-api-key: your-api-key"Anyone with your bridge URL can call its tools, and those calls count toward your usage. Share the URL the way you would share an API endpoint, and keep write operations behind your API's own authentication.
Troubleshooting
- No tools appear. Check that the bridge has at least one tool enabled, and that you restarted the client after editing the config.
- Tool calls return 401 or 403. Your API rejected the request. Check the header name and value the client sends.
- Tool calls return 402. The account has reached its monthly tool-call limit.