MCP

Connect an MCP client to Andy's authenticated tenant operations.

Outcome

Connect an MCP client to Andy’s public tenant operations with the same schemas and stable problems as HTTP and CLI.

Prerequisites

• A supported MCP client.
• A User session or narrowly scoped Workspace API Key.
• The exact Workspace selected for the connection.

Configure the connection

{
  "mcpServers": {
    "andy": {
      "url": "https://app.andypartner.com/api/mcp",
      "headers": { "Authorization": "Bearer ${ANDY_API_KEY}" }
    }
  }
}

Each andy_* tool is generated from the tenant-operation catalog with matching input/output schemas, stable problems, request IDs, authorization checks, and idempotency rules. Workspace API Keys can call only operations allowed by their scopes and owning Workspace.

Machine-readable verification

Use andy-partner/operations.json or the generated CLI Reference to compare every advertised MCP name and schema. Invoke andy_identity_status and require data.status to be ready with a meta.requestId.

Next step

Choose an operation from the CLI Reference. This documentation site does not expose an Ask AI route or a separate documentation MCP server.