Skip to main content

Remote MCP

The Atlan Remote MCP server is a hosted, per-tenant implementation of the Model Context Protocol (MCP). It provides a secure bridge between Atlan's metadata platform and AI tools, so users can query, search, and update metadata directly from their preferred environments.

Unlike the Local MCP server, which requires you to run a service on your own machine, the Remote MCP server is fully managed and hosted by Atlan. This means:

  • No installation or infrastructure setup is required
  • Authentication and authorization are handled through the same policies and permissions you already use in Atlan
  • Integrations can be enabled quickly across your organization without developer-level setup

The Remote MCP server is designed to support both interactive AI experiences (for example, searching metadata through Claude or Cursor) and automation workflows (for example, using n8n, Windsurf, or Microsoft Copilot Studio).

info

Remote MCP is enabled for all Atlan tenants.

Supported connectors​

Remote MCP can be integrated with a range of AI assistants and automation frameworks. Each connector has its own setup guide.

Interactive AI tools​

🧑‍💻Cursor

Integrate Atlan metadata into the Cursor editor for search, lineage, and updates.


View setup guide →

💬Claude

Use Atlan metadata directly in Claude conversations in the browser, and configure Claude Desktop via the same guide.


View setup guide →

💡ChatGPT

Connect Atlan as a Remote MCP server in ChatGPT to search, inspect, and update metadata from chat.


View setup guide →

✨Gemini

Use Gemini with Atlan's Remote MCP server to retrieve and act on metadata directly from Gemini conversations.


View setup guide →

🧱VS Code

Integrate Atlan metadata into your development workflow using VS Code with Remote MCP.


View setup guide →

Automation and workflow tools​

🔁n8n

Automate workflows and service-to-service integrations using Atlan metadata in n8n.


View setup guide →

🌊Windsurf

Bring Atlan metadata into automation and AI-driven flows in Windsurf.


View setup guide →

🧩Microsoft Copilot Studio

Extend Copilot flows with Atlan metadata context using the Remote MCP server.


View setup guide →

🤖Google ADK

Connect agents built with Google Agent Development Kit to Atlan for natural-language asset discovery, lineage, and governance.


View setup guide →

Limiting Remote MCP to read-only operations​

By default, the Remote MCP server exposes both read and write tools. However, if your use case requires read-only access—for example, when running internal agents that only search and explore metadata without making changes—you can request that write tools be disabled for your tenant.

To enable read-only mode:

  1. Submit a support ticket with your request
  2. Once configured by Atlan, the following tools remain available:
    • Search & discovery: Query and filter assets
    • Lineage & exploration: Traverse metadata relationships

All write, admin, and lifecycle tools become inactive, ensuring your agents can safely access metadata without risking unintended changes.

How Remote MCP sources data​

Remote MCP doesn't store or cache metadata itself. Instead, it acts as a bridge to Atlan's REST APIs—the same APIs powering the Atlan SDK and user interface. When you query metadata through MCP:

  1. The request is sent to Atlan's metadata storage layer
  2. Data is retrieved in real time with no intermediate caching
  3. Results reflect the exact state of your metadata at that moment
  4. No additional validation or transformation is applied by the MCP layer

This means your results are:

  • Real-time: No stale data or caching delays
  • Authoritative: Accurate to what's currently stored in Atlan
  • Consistent: Aligned with what you see in the UI and SDK