Atlan MCP Server
HTTP-SSESTDIOModel Context Protocol server for interacting with Atlan services.
Model Context Protocol server for interacting with Atlan services.
The Atlan Model Context Protocol server allows your AI agents to interact with Atlan services.
Tool | Description |
---|---|
search_assets | Search for assets based on conditions |
get_assets_by_dsl | Retrieve assets using a DSL query |
traverse_lineage | Retrieve lineage for an asset |
update_assets | Update asset attributes (user description and certificate status) |
Mac installation
# Install homebrew (if not already installed) /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" # Add Homebrew to your PATH (if not already done) echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> ~/.zprofile eval "$(/opt/homebrew/bin/brew shellenv)" # Install Python 3.11 brew install [email protected] # Verify installation python3 --version # Should show Python 3.11.x
# Mac brew install uv # Verify installation uv --version
# Clone the repository git clone https://github.com/atlanhq/agent-toolkit.git cd agent-toolkit/modelcontextprotocol # Create and activate a virtual environment uv venv source .venv/bin/activate # On Mac/Linux # Install dependencies uv sync
# Mac # Download Docker Desktop from https://www.docker.com/products/docker-desktop # Follow the installation wizard # Verify installation in the terminal docker --version docker compose version
# Mac # Install Colima brew install colima # Start Colima colima start # Install Docker CLI brew install docker # Verify installation docker --version # Build the latest Atlan MCP server image git clone https://github.com/atlanhq/agent-toolkit.git cd agent-toolkit/modelcontextprotocol docker build . -t atlan-mcp-server:latest
,
) or click on Claude in the top left menu and select "Settings"claude_desktop_config.json
highlighted..cursor
directory in the root of your workspace (if not present already)mcp.json
file inside the .cursor
directorymcp.json
based on the server deployment method you chose earlier{ "mcpServers": { "Atlan MCP": { "command": "uv", "args": [ "run", "/path/to/your/agent-toolkit/modelcontextprotocol/.venv/bin/atlan-mcp-server" ], "env": { "ATLAN_API_KEY": "your_api_key", "ATLAN_BASE_URL": "https://your-instance.atlan.com", "ATLAN_AGENT_ID": "your_agent_id" } } } }
Note:
/path/to/your/agent-toolkit
with the actual path to your cloned repositoryyour_api_key
, your_instance
, and your_agent_id
with your actual Atlan API key, instance URL, and agent ID(optional) respectively{ "mcpServers": { "atlan": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "ATLAN_API_KEY=your_api_key", "-e", "ATLAN_BASE_URL=https://your-instance.atlan.com", "-e", "ATLAN_AGENT_ID=your_agent_id", "atlan-mcp-server:latest" ] } } }
Note:
your_api_key
, your_instance
, and your_agent_id
with your actual Atlan API key, instance URL, and agent ID(optional) respectively-e MCP_TRANSPORT=sse
Even though Claude Desktop/Cursor don't yet support remote MCP clients, you can use the mcp-remote local proxy to connect it to your remote MCP server. This lets you to test what an interaction with your remote MCP server will be like with a real-world MCP client.
{ "mcpServers": { "math": { "command": "npx", "args": ["mcp-remote", "https://hosted-domain"] } } }
Want to develop locally? Check out our Local Build Guide for a step-by-step walkthrough!
spawn uv ENOENT {"context":"connection","stack":"Error: spawn uv ENOENT\n at ChildProcess._handle.onexit
, it is most likely this issue where Claude is unable to find uv. To fix it:
which uv
to verify the installation pathwhereis uv
and use that path