> ## Documentation Index
> Fetch the complete documentation index at: https://platform.atlan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP cookbook

> Connect supported clients to Atlan MCP and select the tools they need.

Use this cookbook to connect a coding harness or agent framework to Atlan MCP,
confirm the tools it can use, and choose a safe first task.

## Before you begin

You need access to the workspace where you will use the tools. Your client
authenticates through its OAuth sign-in flow. Follow the client-specific guide
for the appropriate setup.

## Choose your client

Open the integration guide for the client that runs your agent. Each guide
explains its connection settings, authentication, verification, and known
limits.

<CardGroup cols={2}>
  <Card title="Claude Code" icon="https://mintcdn.com/atlan-602e2b74/pPcK1s6Qs7BTlBW2/assets/integrations/claude.svg?fit=max&auto=format&n=pPcK1s6Qs7BTlBW2&q=85&s=3d6e920914e126cf26cf379859af5dfb" href="/integrations/claude-code" width="32" height="32" data-path="assets/integrations/claude.svg">
    Make Atlan MCP tools available in a Claude Code session.
  </Card>

  <Card title="Codex" icon="https://mintcdn.com/atlan-602e2b74/pPcK1s6Qs7BTlBW2/assets/integrations/openai.svg?fit=max&auto=format&n=pPcK1s6Qs7BTlBW2&q=85&s=cb2b7173992862e45da3113c20014e5c" href="/integrations/codex" width="24" height="24" data-path="assets/integrations/openai.svg">
    Give Codex access to the tools available to your identity and workspace.
  </Card>

  <Card title="OpenAI Agents SDK" icon="https://mintcdn.com/atlan-602e2b74/pPcK1s6Qs7BTlBW2/assets/integrations/openai.svg?fit=max&auto=format&n=pPcK1s6Qs7BTlBW2&q=85&s=cb2b7173992862e45da3113c20014e5c" href="/integrations/openai-agents-sdk" width="24" height="24" data-path="assets/integrations/openai.svg">
    Load Atlan MCP tools in an OpenAI SDK agent.
  </Card>

  <Card title="LangGraph" icon="https://mintcdn.com/atlan-602e2b74/pPcK1s6Qs7BTlBW2/assets/integrations/langgraph.svg?fit=max&auto=format&n=pPcK1s6Qs7BTlBW2&q=85&s=c895ab5aab631cbc6be58cc562eeb969" href="/integrations/langgraph" width="63" height="63" data-path="assets/integrations/langgraph.svg">
    Add Atlan MCP tools to a graph or agent node.
  </Card>

  <Card title="CrewAI" icon="https://mintcdn.com/atlan-602e2b74/pPcK1s6Qs7BTlBW2/assets/integrations/crewai.svg?fit=max&auto=format&n=pPcK1s6Qs7BTlBW2&q=85&s=84cc0210decf8030d0eabcd0f7ffeaca" href="/integrations/crewai" width="48" height="48" data-path="assets/integrations/crewai.svg">
    Connect a CrewAI agent to Atlan MCP tools.
  </Card>

  <Card title="Google ADK" icon="https://mintcdn.com/atlan-602e2b74/pPcK1s6Qs7BTlBW2/assets/integrations/google.svg?fit=max&auto=format&n=pPcK1s6Qs7BTlBW2&q=85&s=16fac321f7e3207c93f65cb041d9de20" href="/integrations/google-adk" width="118" height="120" data-path="assets/integrations/google.svg">
    Make Atlan MCP tools available through `McpToolset`.
  </Card>
</CardGroup>

## Connect and discover tools

Configure the client to use Streamable HTTP at
[`https://agentgateway.atlan.engineering/mcp`](https://agentgateway.atlan.engineering/mcp),
then complete its OAuth sign-in flow. A successful connection initializes the
MCP session and lets the client list the tools available to the authenticated
identity and workspace.

Call `registry__initialise` once when a working session starts. Pass the returned
`mcp_session_id` on later calls so reviewers can follow the session as one unit.
The session ID is optional on each call. Tool schemas require a concise
`rationale` by default; a Gateway operator can disable that requirement.

The `/mcp` endpoint names tools as `<server>__<tool>`. Registry's built-in
`search` tool is therefore advertised as `registry__search`. Downstream server
names vary by account.

Read each tool's description and input schema before using it. Select only the
tools your workflow needs. A smaller tool set makes an agent easier to review
and reduces the chance of an unintended change.

Platform-provided tools can be owned by Registry or by an installed extension.
Tools from registered downstream servers are discovered from their server. Your
client's live `tools/list` result is authoritative for callable names and input
schemas, so inspect it before constructing a call.

## Verify with a read-only task

Confirm that the client lists the expected tools, then use a read-only task
before allowing a workflow to make changes. For example, search for an
existing item or inspect an item the agent has already found. If the expected
tools are missing, confirm the selected workspace and the client's
authentication before changing the workflow.

## Manage servers and inspect the catalog

Use the **MCP** category in the [API reference](/developers/api-reference) to
list registered servers, inspect one server, test its availability, and browse
the tool catalog. Use that reference when an application needs to manage a
server or verify its tools outside an MCP client.

## Use the tool reference

The tool pages in this tab describe Registry's current built-in tools. They
cover discovery, artifact lifecycle, containers, relationships, and aggregate
trace statistics. Skill creation and reads now use the generic artifact tools.

For a tool from a registered downstream server, inspect the server record and
your live `tools/list` result before granting it to an agent.