Skip to main content
Bullring exposes its documentation through a public Model Context Protocol server. Compatible AI agents can search and retrieve the API documentation without manually copying pages.

Server endpoints

Public MCP server:
Discovery document:
The discovery document allows compatible clients to locate the MCP server automatically.

What it provides

The MCP server provides documentation context, including:
  • Authentication and request-signing rules.
  • API operations and schemas.
  • Deposit, recipient, withdrawal, and quote workflows.
  • Convoy webhook verification.
  • Error, idempotency, and production guidance.
It retrieves documentation only. It does not execute Bullring API requests, create payments, validate accounts, or access private credentials.

Connect from an MCP-compatible client

Use the client’s remote HTTP MCP server configuration with:

OpenCode

Add the server through OpenCode’s MCP configuration or use the discovery URL:
After connecting, ask the agent to search the Bullring documentation before implementing an integration.

Claude Code

Add the remote MCP server in Claude Code using:
Then verify it with Claude Code’s MCP status command.

Cursor, Codex, and other clients

Add a remote HTTP MCP server named bullring-docs and use:
Client configuration screens and file locations vary by harness. Prefer the client’s remote MCP or discovery configuration rather than copying the complete documentation into a prompt.