MCP gateway
Register tool servers once and make their tools available to every model you route.
What is MCP gateway?
An MCP gateway connects AI models to Model Context Protocol (MCP) tool servers. You register each tool server once, and its tools can then be used by any model routed through the gateway. Access and calls are meant to be controlled and logged in one place. Spro's MCP gateway is planned and not yet available.
Every model integration that needs tools repeats the same setup: connect to the tool server, describe its tools, and handle auth. An MCP gateway puts that setup in one registry, so each tool server is configured once for all models.
This page describes planned behaviour. Details such as supported transports and access rules will be published with the feature.
Key features
What this feature does for your requests.
- Register MCP tool servers once
- Expose their tools to any model you route
- One place to manage tool access
- Tool use recorded alongside model requests
How it works
4 steps, from setup to the first request.
- 01
Register a tool server
Add the MCP server once to the gateway.
- 02
Choose where it is available
Decide which models and keys can use its tools.
- 03
Models call the tools
Tool calls go through the gateway.
- 04
Review the activity
Logs show which tools were used and by which request.
Is it the right fit?
Specific situations where this feature helps, and where it does not.
Good fit if
- Agents need the same tools across several models
- Tool access must be controlled and logged in one place
- Credentials for tool servers should stay away from the models
Not a good fit if
- Your app calls no tools
- You run one model with one tool that is already wired in
- The tools must run inside your own network and cannot be reached through a gateway
MCP gateway FAQs
Common questions about MCP gateway.
Route every AI request through SPRO.
One OpenAI-compatible API for 350+ models, with intelligent routing, 29 built-in guardrails, observability, and automatic failover.
