Skip to main content
Connect any MCP client to one URL. Your client then sees Atlan’s platform tools and every MCP server your team has registered, with no server credentials in its config.

Before you begin

  • A client that supports the Streamable HTTP transport.
  • An Atlan account with access to the workspace you will work in.
  • The gateway endpoint:

Add the gateway to your client

Then run /mcp in a session and complete sign-in for atlan. For the Atlan plugin and its skills, see Claude Code.

Sign in

Choose how your client authenticates. For OAuth, the gateway answers an unauthenticated request with 401 and points the client to https://api.atlan.com/.well-known/oauth-protected-resource/mcp (RFC 9728). MCP clients that support OAuth 2.1 follow it without extra configuration. For bearer tokens, see Authentication for the supported credential paths.

Open a session and make your first call

The gateway ties every tool call to a session, so the audit trail can show who did what and why.
1

List tools

Your client runs tools/list after sign-in. Confirm that you see registry__initialise and the other registry__ tools.
2

Open a session

Call registry__initialise once when work starts. It returns a session_id that starts with mcp_session_.
3

Call tools with the session

Pass session_id and a short rationale on every later call:
Most agents do this without being told. The gateway adds session_id and rationale to every tool’s input schema, and the tool descriptions explain both fields.

Expected result

Your client lists Atlan platform tools plus the tools of every enabled server you can access. A read-only call such as registry__search_artifacts returns results, and the call appears in Tool calls in the MCP Gateway studio.

Troubleshooting

Next steps

Integrations

Put your own MCP servers behind the same endpoint.

Track usage and audit

See every call across every server.