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

# Connect via MCP

> Connect the AMLYZE documentation MCP server to your AI assistant to search and read the docs without leaving your editor.

The AMLYZE documentation is available as a **Model Context Protocol (MCP) server**. Connecting it lets your AI assistant search and read these docs directly — endpoint contracts, field definitions, validation rules, and error codes — as live context while you build your integration.

## What it is

MCP is an open standard that lets AI tools pull in external sources of context. The AMLYZE docs site exposes an MCP server, so any MCP-compatible assistant — Claude Code, Claude Desktop, Cursor, VS Code, and others — can query this documentation on demand instead of relying on a model's training snapshot.

<Info>
  The server is **read-only** and exposes only the public documentation you already see on this site. It does not expose account data, customer data, API tokens, or any other credentials.
</Info>

## What you can do

Once connected, your assistant can:

* **Search the docs semantically** — ask a question in plain language and pull the most relevant pages.
* **Read full pages and API-reference detail** — request and response shapes, field-level descriptions, validation rules, and error codes — straight into your IDE or chat.
* **Stay current** — answers reflect the live documentation rather than a model's training cut-off.

## Server URL

Your MCP server URL is `https://api.amlyze.com/mcp`.

<Info>
  Mintlify auto-hosts the MCP server at `/mcp` for the deployed documentation domain. Before publishing, confirm the server is enabled and reachable at this address.
</Info>

## Connect your client

<Tabs>
  <Tab title="Claude Code">
    <Steps>
      <Step title="Add the server">
        Run this in your terminal:

        ```bash theme={null}
        claude mcp add --transport http amlyze-docs https://api.amlyze.com/mcp
        ```
      </Step>

      <Step title="Verify">
        Run `claude mcp list` (or `/mcp` inside a session) and confirm `amlyze-docs` appears. See the [Claude Code MCP docs](https://docs.anthropic.com/en/docs/claude-code/mcp) for details.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Codex">
    <Steps>
      <Step title="Add the server to config.toml">
        Create or update your Codex `config.toml` (project-level `.codex/config.toml`, or global `~/.codex/config.toml`):

        ```toml theme={null}
        [mcp_servers."amlyze-docs"]
        url = "https://api.amlyze.com/mcp"
        ```
      </Step>

      <Step title="Restart Codex">
        Restart Codex so it picks up the new server.
      </Step>

      <Step title="Verify">
        Run `/mcp` and confirm `amlyze-docs` is in the configured MCP servers.
      </Step>
    </Steps>

    <Note>
      Prefer the `config.toml` entry over `codex mcp add --url`: some hosted MCP providers trigger an OAuth flow even when the documentation endpoint is publicly readable.
    </Note>
  </Tab>

  <Tab title="GitHub Copilot CLI">
    <Steps>
      <Step title="Add the server">
        Run this in your terminal:

        ```bash theme={null}
        copilot mcp add --transport http amlyze-docs https://api.amlyze.com/mcp
        ```
      </Step>

      <Step title="Restart Copilot CLI">
        Restart Copilot CLI so it picks up the new server. Skipping this can trigger an OAuth prompt, even though the docs endpoint is public.
      </Step>

      <Step title="Verify">
        Run `/mcp` in Copilot CLI and confirm `amlyze-docs` is listed. See the [Copilot CLI MCP docs](https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers) for details.
      </Step>
    </Steps>
  </Tab>
</Tabs>

<Note>
  **Quickest path:** on any page of this site, open the contextual menu in the page header and choose **Copy MCP install command** to copy the install command, or **Copy MCP server URL** to grab the URL directly — no need to type it by hand.
</Note>

<Warning>
  Client MCP setup changes frequently. Verify the exact command or configuration against each client's current MCP documentation before relying on it.
</Warning>