1
key for everything
Grab your API key
Use the same key from your InferenceSaver dashboard. No separate MCP credential to manage.

One remote MCP server, on the same routing layer as our API. Point Claude, Cursor, or Windsurf at it and let the model pick the cheapest provider automatically.
The Model Context Protocol is an open standard for connecting AI assistants to external tools and data. Instead of every app building its own integration with every service, an MCP server exposes a fixed set of tools once, and any MCP client — Claude Desktop, Claude Code, Cursor, Windsurf — can call them the same way.
Four tools, all gated behind your own API key. No anonymous access to models or spend.
list_capabilitiesDiscover every tool available through the InferenceSaver MCP server.

list_modelsBrowse every model available on InferenceSaver, filtered by provider or capability, with live pricing.

get_modelInspect the capabilities, controls, and pricing for one model.

get_model_statusRead auditable health, uptime, latency, capability, and pricing data for available models.

search_documentationSearch published InferenceSaver documentation from your AI client.

get_documentationRead a published documentation page by its stable path.

chat_completionRun a chat completion through the routing layer. The cheapest available provider is picked automatically.

start_image_generationCreate images with the image models available to your API key.

start_video_generationStart short-form video generation and receive a pollable job reference.

start_voiceover_generationTurn text into speech with selectable models, voices, and output formats.

start_music_generationStart music generation from a prompt, lyrics, and production controls.

get_generation_jobCheck video or music generation status and retrieve outputs.

get_usagePull recent token usage for the authenticated account, straight from the source.

get_balanceCheck the current credit balance without leaving the assistant.

Same key, one URL, and you're routing through every model on InferenceSaver.
1
key for everything
Use the same key from your InferenceSaver dashboard. No separate MCP credential to manage.

60s
typical setup time
Add https://mcp.inferencesaver.com as a remote MCP server in Claude, Cursor, Windsurf, or any MCP-compatible client.

0
extra credentials to manage
Pass your API key as a Bearer token. Every tool call runs under your account, with your usage and your rates.

1
key for everything
Use the same key from your InferenceSaver dashboard. No separate MCP credential to manage.

60s
typical setup time
Add https://mcp.inferencesaver.com as a remote MCP server in Claude, Cursor, Windsurf, or any MCP-compatible client.

0
extra credentials to manage
Pass your API key as a Bearer token. Every tool call runs under your account, with your usage and your rates.

1
key for everything
Use the same key from your InferenceSaver dashboard. No separate MCP credential to manage.

60s
typical setup time
Add https://mcp.inferencesaver.com as a remote MCP server in Claude, Cursor, Windsurf, or any MCP-compatible client.

0
extra credentials to manage
Pass your API key as a Bearer token. Every tool call runs under your account, with your usage and your rates.

1
key for everything
Use the same key from your InferenceSaver dashboard. No separate MCP credential to manage.

60s
typical setup time
Add https://mcp.inferencesaver.com as a remote MCP server in Claude, Cursor, Windsurf, or any MCP-compatible client.

0
extra credentials to manage
Pass your API key as a Bearer token. Every tool call runs under your account, with your usage and your rates.

No. Use the same API key from your InferenceSaver dashboard. Every tool call runs under your existing account, balance, and rate limits.
Any MCP-compatible client that supports remote Streamable HTTP servers: Claude Desktop, Claude Code, Cursor, and Windsurf all work out of the box.
Every tool call is gated behind your Bearer token and shows up in your usage logs immediately. There is no anonymous or shared access to models.
Yes. mcp.inferencesaver.com sits on top of the exact same routing and pricing as api.inferencesaver.com. Same models, same rates, same account.
Get an API key from the dashboard, drop it into your MCP config, and your assistant can route to the cheapest provider for any model — automatically.