Skip to main content
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.
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.

​
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.
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.

​
Connect your client

1

Add the server

Run this in your terminal:
claude mcp add --transport http amlyze-docs https://api.amlyze.com/mcp
2

Verify

Run claude mcp list (or /mcp inside a session) and confirm amlyze-docs appears. See the Claude Code MCP docs for details.
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.
Client MCP setup changes frequently. Verify the exact command or configuration against each client’s current MCP documentation before relying on it.