MCP Server — Documentation for AI

The Axia MCP server exposes this documentation — the Operator Manual, the User Guide and the BaaS API Reference — to AI assistants (Claude, Cursor, Windsurf and others) through the Model Context Protocol (MCP).

In practice: you connect the server to your AI tool and start asking questions in natural language about the platform and the API, with answers grounded in the official documentation, in Portuguese, English and Spanish.

Endpoint: https://docs-mcp.axiadigitalsolutions.com/mcp · Transport: Streamable HTTP · Auth: OAuth 2.1 · Access: read-only

---

1. What is MCP

The Model Context Protocol is an open standard that lets AI assistants securely access external data sources and tools. Instead of copy-pasting documentation snippets, the AI queries the server directly and fetches exactly what it needs to answer.

The Axia server is read-only: it only searches and returns documentation content. It performs no operations, accesses no customer data and changes nothing.

---

2. Available tools

The server offers 6 tools that the AI uses automatically depending on the question:

Tool	What it does
search_docs	Full-text search across the whole documentation (filters by language and collection).
get_page	Returns the full content of a page.
list_sections	Lists the navigation tree (collections and pages).
docs_stats	Collection statistics (pages per language and section).
list_api_endpoints	Lists the BaaS API endpoints (filters by tag or text).
get_api_endpoint	Details an endpoint: parameters, request body and responses.

You don't call these tools manually — just chat, and the assistant decides when to search.

---

3. How to get access (password)

The server is protected by OAuth 2.1 with an authorization password.

Request the password from support

The access password is provided by the Axia support team. Request it at [email protected], stating who will use it and for what purpose.

You do not register a user or create an account: when connecting, your AI tool opens an authorization page where you enter the password received from support — just once. From then on, the session is renewed automatically.

---

4. Connect in Claude (web)

1. Open settings → Connectors.
2. Click Add custom connector.
3. Paste the server URL:

   https://docs-mcp.axiadigitalsolutions.com/mcp

4. Claude opens the authorization page. Enter the password provided by support and confirm.
5. Done — the 6 tools appear and Claude starts consulting the documentation in your chats.

Custom connectors require a paid Claude plan (Pro/Max/Team/Enterprise). On Team/Enterprise accounts, the organization admin must enable custom connectors.

---

5. Connect in Claude Code / Desktop

Via the Claude Code CLI:

claude mcp add --transport http axia-docs https://docs-mcp.axiadigitalsolutions.com/mcp

The client runs the authorization flow and opens the browser for you to enter the password. To confirm:

claude mcp list        # should show "axia-docs: ✓ connected"

Or, via a configuration file (project .mcp.json, or the Desktop config):

{
  "mcpServers": {
    "axia-docs": {
      "type": "http",
      "url": "https://docs-mcp.axiadigitalsolutions.com/mcp"
    }
  }
}

Other MCP-over-HTTP clients (Cursor, Windsurf, VS Code) use the same url format.

---

6. Usage examples

Once connected, just ask naturally. The assistant combines the tools on its own (search → read → answer).

BaaS API integration

How do I create a PIX charge in the API? Show the endpoint and the request body.
Detail POST /v1/bank-accounts/create — which fields are required?
Generate a Node.js example to create a digital account and check the balance.
How do crypto webhooks work? What payload do I receive?

Operator Manual (BackOffice)

How does the operator approve a manual payment? Step by step.
What does the antifraud module do and which permissions do I need?

User Guide / multi-language

Give me the PIX documentation in Spanish.
Summarize the credit manual in English.

Ask for the source

End with "...and cite the documentation page you used". Results carry the path/URL, so the assistant can link the source.

---

7. Security and limits

• Read-only — the server only fetches content; it performs no operations and accesses no customer data.
• OAuth 2.1 + PKCE — access is authorized by token; the password only unlocks the initial authorization.
• Documentation content — answers reflect the published documentation; for the exact API contract, the source of truth is the Interactive reference.
• Updates — the indexed base is updated along with the documentation. Queries always return the latest published content.

---

8. Support

• Access password and provisioning: [email protected]
• API questions: see Error Handling and the Interactive reference