> ## 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. > ## Agent Instructions > To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the SDK. To install or publish skills from a terminal, use the `aireg` CLI; `aireg --map json` prints its command map. The `atlanai` CLI is deprecated. Run a read-only identity check before any write. > The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects. > SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript. > These docs cover Atlan AI Registry, Atlan's hosted product. The AI registry specification and aireg CLI are maintained separately. /open-source lists publicly reachable signed installers and explains that the source repository and hosted CLI reference currently require GitHub access. Do not claim the repository or its reference docs are publicly accessible. Use these docs for Atlan-specific setup such as the adapter, sign-in and workspaces. # Integration catalog > Find the supported connection type and the check that proves it works. An integration can connect a client to Atlan, connect Atlan to another service, or export telemetry. Use the type below to find its setup and verification path. | Type | Integrations | What Atlan does | Verify | | - | - | - | - | | Coding clients | Claude Code, Codex, Cursor, VS Code, other Streamable HTTP MCP clients | Serves permitted MCP tools; coding-client trace capture is a separate setup | Connect the server, list tools, make a read-only call, and find it in MCP activity | | Agent frameworks | LangGraph, OpenAI Agents SDK, Google ADK, CrewAI, pi, Pydantic AI, Vercel AI SDK | Connects tools and/or traces according to the framework guide | Run one agent request, flush tracing, and inspect its root and child spans | | Model providers | OpenAI, Anthropic, OpenRouter, Bedrock, Vertex AI, Google AI, Azure, OpenAI-compatible endpoints, LiteLLM, TypeSafe | Discovers models and routes supported inference | List callable models and send one request for the intended modality | | Remote MCP servers | A public Streamable HTTP server your team registers | Discovers and proxies its tools using shared or per-user credentials | Test or refresh the server, inspect live `tools/list`, and make a permitted call | | Collaboration | Slack | Serves personal Slack tools and creates authorized Atlan link previews | Check each connection separately; make a tool call or share a permitted test link | | Source control | GitHub App | Imports selected repository metadata and recent activity | Connect a repository to a workspace and inspect its synchronization status | | Data-platform clients | Databricks, Snowflake | Serves Atlan as an external MCP server | Add Atlan to the platform's agent and confirm a Registry tool call | | HTTP APIs | Registered HTTP/REST endpoints | Injects a linked credential and forwards requests to the configured base URL | Call the source API's documented read-only route through the proxy | | Telemetry | OpenTelemetry SDKs, compatible instrumentors, direct OTLP/HTTP | Receives spans with Atlan identity and context | Flush export and retrieve the expected trace | | Evaluation runners | atlanai SDK Eval, pytest, Vitest, Node.js test runner, custom harnesses | Records experiment results and joins them to traces | Complete a small experiment and inspect its result and trace join | Browse [MCP integration templates](/integrations/references/mcp-connectors) for each catalog entry, logo, authentication requirement, and endpoint. ## Support boundaries A remote MCP registration is not a built-in connector for every feature of that service. Its authenticated `tools/list` defines the available tools. The gateway does not host local stdio servers or translate every third-party API into tools. A framework's tracing support does not imply model routing or MCP setup. Follow the parts of its guide that match your application. [Framework coverage](/frameworks/coverage) distinguishes tested adapters, compatible telemetry, and manual tracing. A logo identifies the product the guide connects. It does not imply that the vendor certifies the integration. ## Choose a guide Connect a client with your Atlan identity. Choose the tracing path for your runtime. Check endpoint and credential requirements. Register and inspect a remote tool catalog. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.