Skip to content
Scalekit Docs
Talk to an Engineer Dashboard

What is Agent Gateway

Agent Gateway gives your team one MCP URL for Claude, ChatGPT, Cursor and other AI tools, with each person signed in and access set per connection.

Agent Gateway gives your team’s AI tools governed access to the apps your company uses. You enable it in the Scalekit dashboard and get one MCP endpoint URL. Each person adds that URL to their AI client, such as Claude, ChatGPT, Cursor or VS Code, and signs in with their own account. The tools they see come from the connections you add, filtered by the groups they belong to.

Agent Gateway is for the admins who give their own team access to AI tools, such as IT or security teams. Everything is set up in the dashboard, with no code. Building an agent into your own product for your customers? See AgentKit.

Both products use the same connectors. They differ in who builds the agent and who uses it.

AgentKitAgent Gateway
You want toLet your product’s agent act in your customers’ appsGive your team’s AI tools access to your company’s apps
Who sets it upDevelopers, in codeAdmins, in the dashboard
Who signs inYour customers, through your appYour team, with their own accounts
The agentOne you build and hostExisting AI clients, such as Claude, ChatGPT, Cursor or VS Code
How tools are reachedSDK, REST API or a Virtual MCP serverOne MCP endpoint URL for the whole team
Access controlYour code chooses the tools for each callGroups and per-connection policies

Use AgentKit when you’re building a product, such as an inbox assistant or a sales copilot, and your users connect their accounts inside your app. Start with the AgentKit quickstart.

Use Agent Gateway when people on your team already use AI tools and need them to read and act in company apps, with you deciding who can use which tools.

Protecting an MCP server you built yourself? That’s MCP Auth.

  1. You enable the Gateway in an environment. Scalekit creates its MCP endpoint and adds you as its first user.
  2. You add connections, such as Gmail, Outlook, Slack or GitHub. These are the same connections AgentKit uses, set up once for the environment.
  3. Each person connects their AI client to the MCP endpoint URL and signs in. The client asks for their consent the first time it acts for them.
  4. Each person connects their own app accounts. The first time a tool needs an app the person hasn’t connected, the AI client gives them a link to connect it.
  5. Groups decide which tools each person sees. On each connection you choose which groups can use it, and whether they get every tool or only some.

Tool calls through the Gateway appear under Overview and Logs in the dashboard.

TaskWhereGuide
Enable the Gateway and get its URLGetting StartedQuickstart
Connect Claude, ChatGPT, Cursor and moreThe URL from SettingsConnect AI clients
Add users, SSO and SCIMIdentityUsers and access
Decide who can use which toolsGroups, and each connection’s Policies tabAccess policies
Review plans and limitsBillingPlans and limits

Enable the Gateway and connect your first AI client in the Quickstart.