Skip to main content
Without a gateway, every person sets up every MCP server in every tool they use, and each one keeps its own tokens. Nobody can see which agent called which tool, and taking access away means chasing down every config file. MCP Gateway gives everyone one URL instead:
Add it to Claude Code, Cursor, VS Code, Codex, or your own agent and sign in. The agent gets Atlan’s tools and every MCP server your team has added that you’re allowed to use. Admins add a server once, for the whole organization.
Your clients, such as Claude Code, Codex, Cursor and VS Code, agent frameworks, and your own agents, connect to one endpoint, https://api.atlan.com/mcp. Atlan MCP Gateway provides OAuth 2.1 sign-in, one catalog with namespaced tools, a workspace permission check on every call, credentials held at the gateway, session and call audit, and rate limits and timeouts. Behind it are Atlan platform tools and your registered MCP servers.Your clients, such as Claude Code, Codex, Cursor and VS Code, agent frameworks, and your own agents, connect to one endpoint, https://api.atlan.com/mcp. Atlan MCP Gateway provides OAuth 2.1 sign-in, one catalog with namespaced tools, a workspace permission check on every call, credentials held at the gateway, session and call audit, and rate limits and timeouts. Behind it are Atlan platform tools and your registered MCP servers.

What you can do

  • Roll out a tool to everyone at once. Add Linear, Notion, Glean, or your own server once. Every connected agent can use it the next time it looks for tools.
  • Let people act as themselves. A server can sign each person in with their own account, so a Linear issue an agent files shows the real author.
  • Control who can use what. Access follows workspaces — if you can see a workspace, you can see its tools; if you can edit it, you can run them.
  • See what agents did. Each tool call is recorded with who made it, which tool, the reason the agent gave, and whether it worked.
  • Keep agents fast as your tool list grows. Agents search for the tools they need instead of loading hundreds of tool descriptions up front.

Get started

Connect your coding tool or agent

DeveloperAdd the MCP URL to Claude Code, Cursor, VS Code, or Codex, sign in, and make your first audited tool call.

Add MCP servers for your team

AdminPublish Linear, Notion, Snowflake, or your own server once. Everyone who connects gets it, with their own access level.

Set who can access each server

AdminAccess follows workspace membership. See how to scope tool visibility and run permissions per server.

Review what agents did

AdminSee every tool call — who made it, which tool, the reason given, and how it ended. Sessions group calls for one task.
If something fails, see MCP Gateway errors.

How agents reach your servers

MCP Gateway is an MCP server that Atlan hosts. Your client connects to it. For each server your organization registered, the gateway makes the call to that server itself, with the credential stored for it. So Atlan needs to reach each registered server over Streamable HTTP, and your client doesn’t. Only the calls a client sends to https://api.atlan.com/mcp go through the gateway. A client can hold other MCP connections at the same time. These are the two usual ways to wire it: Atlan’s metric and ontology tools return definitions and context. They don’t run SQL. In every setup, your agent or your warehouse runs the query.

Make agents ask Atlan first

MCP has no setting that orders servers. The model picks a tool from the names and descriptions it sees, so you steer it with instructions:
  • Standing instructions. In agent setup, Instructions for your agents are added to every session of the AI tools you use with Atlan Trident. For example: “For a question about business data, look up the metric definition in Atlan before you query the warehouse.” See Choose what your AI tools load.
  • A skill. Write the order of steps into a skill the agent loads for that kind of question.
  • Fewer direct connections. A tool the client can’t see can’t be picked first. Registering a server behind the gateway and removing the direct connection leaves one place to look.
Instructions guide the model. They don’t enforce an order.

See also