Connect to Cross River docs via MCP
Ask your AI assistant questions about our APIs, and it answers from our published documentation. Your assistant reads the same docs you do, so you don't have to search through pages or switch tabs to find endpoints, flows and schemas.
Why this matters
Instead of clicking through pages to find what you need, ask your AI assistant.
Want to know which fields are required for a payment? Ask. Need an example request? Ask. Wondering why a transaction failed? Ask.
Your assistant looks up the answer in the documentation instead of relying on what it already knows, which may be out of date.
How it works
Our documentation is served through a Model Context Protocol (MCP) server. AI tools such as Claude Code, Claude Desktop and Cursor connect to it and read our docs directly. Once connected, your assistant can search the documentation, open specific pages and answer questions from their content.
The connection is read-only and needs no API key. It reads only our published documentation, the same content you see at docs.crossriver.com.
Choose the spaces to connect
Our documentation is organized into six spaces, and each MCP connection reads one space. Add one connection for each space you want your assistant to use.
Space | What it covers | API_BASE |
|---|---|---|
APIs | API reference: endpoints, fields, request and response examples, webhooks | https://docs.crossriver.com/apis |
Concepts | How our products work: accounts, cards, payments, onchain payments and lending | https://docs.crossriver.com/concepts |
Tutorials | Step-by-step guides for our APIs and COS Explorer | https://docs.crossriver.com/tutorials |
Get started | Welcome page, quickstarts and sandbox setup | https://docs.crossriver.com |
Ops and admin | Customer onboarding, the Org management portal, COS Explorer, SFTP setup, reports and the glossary | https://docs.crossriver.com/ops-and-admin |
Changelog | Release notes | https://docs.crossriver.com/changelog |
If you build an integration, connect APIs first. It's the only space with the API reference. Add Concepts and Tutorials when you also want answers about how a product works or how to complete a task.
Add the connections
Add the configuration below to your AI tool's MCP settings, keep the spaces you need and delete the rest. Each entry runs the same Archbee MCP server, @archbee/mcp, pointed at a different space. You need Node.js installed so that npx can run it.
{
"mcpServers": {
"crossriver-apis": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@archbee/mcp"],
"env": { "API_BASE": "https://docs.crossriver.com/apis" }
},
"crossriver-concepts": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@archbee/mcp"],
"env": { "API_BASE": "https://docs.crossriver.com/concepts" }
},
"crossriver-tutorials": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@archbee/mcp"],
"env": { "API_BASE": "https://docs.crossriver.com/tutorials" }
},
"crossriver-get-started": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@archbee/mcp"],
"env": { "API_BASE": "https://docs.crossriver.com" }
},
"crossriver-ops-and-admin": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@archbee/mcp"],
"env": { "API_BASE": "https://docs.crossriver.com/ops-and-admin" }
},
"crossriver-changelog": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@archbee/mcp"],
"env": { "API_BASE": "https://docs.crossriver.com/changelog" }
}
}
}Restart your AI tool after you change the configuration.
Each API_BASE must point at a space. https://docs.crossriver.com on its own connects to Get started only, so an assistant connected that way can't see the API reference.
What your assistant can do
Each connection gives your assistant these tools for its space:
- search_title: find pages by title
- search_query: search the content of the space's pages
- get_doc: read the full content of a page
- get_all_docs: read every page in the space at once. This returns a lot of content, so searching is usually the better choice.
When you connect more than one space, your assistant sees one set of tools per connection, labeled with the connection name, such as crossriver-apis.
Example questions
- Show me a complete request and response example for POST /payments.
- Why would a payment return a declined status?
- What fields are required to onboard a customer?
- Show me an example request for POST /customers, including address and contact info.
- What errors can occur when creating a customer?
If your assistant can't find an answer, check that the space that covers the topic is connected. API questions need the APIs space.
Keep in mind
Your assistant reads our documentation, but it can't make API calls or access your account through this connection. The connection is read-only and uses no API key.