Connect Claude Code

Preview Connecting Claude Code to the Atlan MCP endpoint lets a session find registry artifacts, inspect skills, and check what your identity can reach, without leaving the terminal. Use it when you work in Claude Code and want governed tools in the session. It adds tools only; recording sessions and routing model calls are optional setups below.

Before you begin

Before you start, make sure you have:

Claude Code: A current version with remote HTTP MCP support.
Atlan account: Access to the workspaces whose artifacts and tools you expect to use. This integration is in Preview and is not enabled for every account.

Add Atlan MCP endpoint

claude mcp add --transport http atlan https://api.atlan.com/mcp

This connects in search mode, the default: Claude Code sees five tools and asks you to approve a runner instead of each tool by name: mcp__call_read_tool for reads, mcp__call_write_tool for writes that are not destructive, and mcp__call_tool for anything else. To list every tool by name, use "https://api.atlan.com/mcp?tools=full" as the URL. Full mode will be deprecated later.To let reads and writes run without asking and still be asked before anything destructive, add the lookups and the two narrower runners to permissions.allow in .claude/settings.json, or in ~/.claude/settings.json for every project:

{
  "permissions": {
    "allow": [
      "mcp__atlan__mcp__search_tools",
      "mcp__atlan__mcp__describe_tools",
      "mcp__atlan__mcp__call_read_tool",
      "mcp__atlan__mcp__call_write_tool"
    ]
  }
}

Claude Code keeps asking before each mcp__call_tool call. The runner a tool needs comes from the tool’s own labels, so a tool labelled read-only that writes runs through mcp__call_read_tool. See Tool approvals.This adds a server named atlan, private to you in the current project. Add --scope user to use it in every project, or --scope project to share it through the project’s .mcp.json. The configuration holds only the URL; keep credentials out of project files and source code.

Verify connection

Check server: Run claude mcp list and confirm that atlan is connected.
Check tools: Ask a read-only task from Example prompts, such as listing your workspaces. It returns results from the workspaces you can access.

The tools available depend on your account, workspace access, and enabled capabilities, and every call follows the permissions of the signed-in identity. A connected server does not guarantee access to every registry or skill tool.

Example prompts

Each prompt is read-only and uses the tools your identity can reach. Replace the example names with your own. Check what an agent depends on before you change it

Before I change the support agent in this repo, find its record in Atlan and list the skills it uses.

Investigate failing runs

Show the support agent's failed runs from the last day and the spans of the most recent failure.

Pick the right team skill

Find the skills in our platform-team workspace that cover incident reviews and tell me which version of each is live.

Troubleshooting

If sign-in repeats or never completes, see Atlan sign-in repeats or never completes. For a missing server, missing tools, or refused calls, see MCP Gateway errors. For client scopes and connection diagnostics, see the Claude Code MCP documentation.

Next steps

Publish skills from coding agent: Inventory local skills and publish them with aireg.

Connect coding agents

Connect agent frameworks

Connect model SDKs

Connect data platforms

Connect collaboration tools

Docs for AI agents

Before you begin

Example prompts

Troubleshooting

Next steps

See also