MCP Server

Quick Reference

WhatMCP Server for AI tools

WhyQuery A55 docs from AI assistants and IDE integrations

A55 exposes its documentation through a Model Context Protocol (MCP) server. This lets AI assistants, IDE extensions, and automation tools query up-to-date documentation programmatically instead of relying on stale training data.

Why MCP

Use case	Benefit
AI grounding	Get current docs instead of stale training data
IDE integration	Reference A55 docs directly in your editor
Tooling	Structured access for CI/CD and automation scripts
Search	Semantic search across all documentation

Endpoint

https://docs.a55.tech/mcp

MCP client setup

Copy the URL above and paste it into your MCP client configuration. No API key is required for documentation access.

What you can use it for

• Ground AI coding assistant answers in current A55 documentation
• Pull reference snippets for error codes, status definitions, and API fields
• Build internal tooling that validates integration parameters against docs
• Search documentation semantically from terminal or scripts

Configure in AI tools

Cursor IDE

Add to your .cursor/mcp.json:

{
  "mcpServers": {
    "a55-docs": {
      "url": "https://docs.a55.tech/mcp"
    }
  }
}

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "a55-docs": {
      "url": "https://docs.a55.tech/mcp"
    }
  }
}

Generic MCP Client

1. Set the server URL to https://docs.a55.tech/mcp
2. Use the server name label A55 Docs
3. No authentication headers required
4. Connect using SSE (Server-Sent Events) transport

Available resources

Resource	Description
API Reference	Endpoint specifications, request/response schemas
Integration guides	Step-by-step implementation walkthroughs
Status codes	Charge lifecycle states and response codes
Payment methods	Country-specific method documentation
Changelog	API versioning and breaking change history

Read-only docs access

The MCP server provides read-only access to documentation. It does not replace API keys or grant access to the A55 payment API.

Client naming

When configuring your client, use the server name label A55 Docs for consistent identification across tools.

Introduction →Authentication →Integration Overview →