MCP server

These docs are available over MCP. Point your AI coding assistant at one URL, and it reads the documentation directly: the same pages you see here, including the generated API reference with its parameter tables.

What MCP is

MCP (Model Context Protocol) is an open standard for connecting AI assistants to external sources of data. A tool that speaks MCP can call a server, search it, and read what it finds, instead of relying on whatever happened to be in its training data.

That difference matters for an integration. An assistant working from memory invents parameter names, mixes up protocols, and confidently reports formulas that were changed two releases ago. An assistant connected to this server reads the current page.

What the server exposes

Tool	What it does
docs_search	Finds relevant pages and returns their titles, URLs and matching snippets.
docs_fetch	Returns one page in full, as Markdown, by URL.

Both cover the whole documentation: the integration guides, the appendixes with hash formulas, the error reference, and every operation page under API requests with its request parameters, allowed values, constraints and response fields.

The endpoint is public and read-only. No API key, no account, nothing to configure on our side:

https://docs.akurateco.com/mcp

Transport is streamable HTTP, the standard transport for a remote MCP server (as opposed to stdio, used when a server runs as a local process). Your credentials, transactions and account data are never involved: the server only serves documentation.

Connect your tool

The Use in your IDE button in the top navigation copies a ready configuration for about twenty MCP clients. The most common ones are below.

Claude Code

Run this from a terminal:

claude mcp add payments-docs https://docs.akurateco.com/mcp --transport http --scope user

Claude Desktop

The quickest route needs no file editing: Settings → Connectors → Add custom connector, then paste the endpoint URL.

To use the configuration file instead:

1. Open your Claude Desktop configuration file: ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows, ~/.config/Claude/claude_desktop_config.json on Linux.
2. Add the connector to the mcpServers section:

{
  "mcpServers": {
    "payments-docs": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://docs.akurateco.com/mcp"]
    }
  }
}

That file accepts servers started as local processes, so a remote endpoint is reached through the mcp-remote bridge: npx fetches it on first run, and Node.js has to be installed. The in-app connector above talks to the endpoint directly and needs neither.

Cursor

Add to ~/.cursor/mcp.json (%USERPROFILE%\.cursor\mcp.json on Windows):

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

VS Code

Run this from a terminal to register the server:

code --add-mcp '{"name":"payments-docs","type":"http","url":"https://docs.akurateco.com/mcp"}'

Or add the same thing by hand to mcp.json in your VS Code user directory:

{
  "servers": {
    "payments-docs": { "type": "http", "url": "https://docs.akurateco.com/mcp" }
  }
}

Codex

Run this from a terminal:

codex mcp add --url https://docs.akurateco.com/mcp payments-docs

Or add it by hand to ~/.codex/config.toml:

[mcp_servers.payments-docs]
url = "https://docs.akurateco.com/mcp"

Restart the tool after adding the server. Most clients list connected servers and their tools somewhere in settings, which is the quickest way to confirm it worked.

What to ask it

Once connected, ask in plain language and let the assistant pull the pages it needs:

• Which parameters does a SALE request require on S2S CARD, and which are optional?
• How do I compute the hash for a CREDITVOID request?
• What does the callback carry after a 3DS redirect?
• What's the difference between Checkout and Hosted payment fields for PCI scope?
• Which error code means the card was declined by the issuer rather than by us?

If the assistant answers from general knowledge instead of pulling a page, that's usually the tool call not firing on its own. Be explicit and name it directly: "Use docs_fetch and return the full SALE parameters for S2S CARD." Naming the tool gets a more reliable result than a plain question.

It answers from the documentation only. For anything tied to your account (credentials, acquirer setup, pricing, service status), talk to your account manager.

Related

• AI Help: the floating button in the corner of every page answers the same questions in the browser, with nothing to set up.
• API requests: the reference this server serves for every operation.
• modelcontextprotocol.io: the protocol itself, its specification, client list and guides for building your own server.