Budgets and rate limits for paid connectors
Give each paid connector a spend budget and a call rate per team or agent, so one workflow can't run up a vendor bill.
- Spend budget per connector
- Call rate per team or agent
MCP (Model Context Protocol) servers are the connectors agents use to act on real systems. The MCP Gateway keeps them in one curated registry and decides who can call each one, how often and at what cost.
Who calls it
MCP Gateway
Every request, in this order:
MCP servers
Your own servers
Before a call reaches an MCP server, the gateway checks the caller's permissions, the connector's budget and its rate. Calls outside the rules never leave the gateway.
Put each MCP server in the registry once.
Group the tools each team needs into one set.
Decide who can call what, down to single actions.
See every call, what it returned and what it cost.
Three groups of connectors: our own products, the enterprise systems your processes run on, and any partner service or system you work with, so workflows can be automated end to end.
Our own products, ready to connect.
The systems of record your processes run on.
Any partner service or system you work with, so workflows run end to end. Integrations you won't find elsewhere.
Every approved MCP server in one list, organized by category, with its health, the actions it exposes and the agents that use it.
Define which users, teams and agents can call which MCP servers, down to single actions, such as allow read and deny write. Access is set per project and can change at any time.
Each agent sees only the tools it is allowed to use, so it can't call what it can't see.
Bundle chosen tools from several servers into one set, and give that set to a team or an agent.
Every tool call recorded: which agent, which server and action, what came back and how long it took.
See what each tool call costs next to the model spend behind it, by tool, server, team or agent.
Give each paid connector a spend budget and a call rate per team or agent, so one workflow can't run up a vendor bill.
When usage looks anomalous or reaches for sensitive data, the breaker trips and cuts the connector off before the damage spreads.
Start from a template or register any MCP server by its URL. The gateway checks the connection and loads its actions.