Skip to main content
The Zeam platform provides two MCP servers so AI tools can work with your documentation and your API data in a single workflow.

​
What is MCP?

The Model Context Protocol is an open standard that connects AI tools to external data sources and APIs. Any MCP-compatible client — Warp, Claude Desktop, Cursor, VS Code Copilot, and others — can connect to one or both Zeam MCP servers.

​
MCP servers at a glance

Documentation MCP

Search and read the Zeam developer docs from any AI tool.URL — https://docs.zeam.money/mcpNo authentication required.

API MCP

Query wallets, beneficiaries, payment corridors, and Stellar data.URL — https://mcp.zeam.app/sseRequires a bearer token.

​
Documentation MCP

Mintlify hosts a read-only MCP server at https://docs.zeam.money/mcp. It exposes two tools:
  • Search — full-text search across every page of the Zeam developer docs.
  • Query docs filesystem — read page content, browse the docs structure, and batch-read multiple pages.
No API key is needed. Connect the URL in your AI tool and start asking questions about the Zeam platform.

​
Connect the documentation MCP

1

Claude

  1. Open Settings → Connectors → Add custom connector.
  2. Name: Zeam Docs, URL: https://docs.zeam.money/mcp.
  3. Select Add.
2

Claude Code

claude mcp add --transport http zeam-docs https://docs.zeam.money/mcp
3

Cursor

Open Command Palette → Open MCP settings → Add custom MCP and paste:
{
  "mcpServers": {
    "zeam-docs": {
      "url": "https://docs.zeam.money/mcp"
    }
  }
}
4

VS Code

Create .vscode/mcp.json:
{
  "servers": {
    "zeam-docs": {
      "type": "http",
      "url": "https://docs.zeam.money/mcp"
    }
  }
}
You can also use the contextual menu at the top of any page to copy the MCP URL or connect directly to Cursor or VS Code.

​
API MCP

The API MCP server lets AI agents interact with live Zeam data. Query wallets, list beneficiaries, discover payment corridors, and inspect transactions without writing integration code.

​
Use cases

  • Exploration — browse associations, wallets, assets, and beneficiaries interactively while building your integration.
  • Debugging — inspect accounts, transactions, and effects to diagnose payment issues.
  • Prototyping — test connector queries and swap quotes before writing code.
  • Agentic workflows — build AI agents that query Zeam data, generate quotes, and prepare payment instructions.

​
Available tools

The API MCP server exposes tools across three domains.

​
Platform

  • zeam_whoami — returns your authenticated identity and token scopes.
  • zeam_list_associations — lists associations (business entities) you have access to.
  • zeam_get_association — returns a single association by ID.
  • zeam_list_wallets — lists wallets, optionally filtered by association.
  • zeam_get_wallet — returns a single wallet (raw or DTO view).
  • zeam_list_assets — lists assets visible to your principal.
  • zeam_list_beneficiaries — lists beneficiaries with optional search, type, and method filters.
  • zeam_get_beneficiary — returns a single beneficiary by association and ID.

​
Connect (payment routing)

  • zeam_connect_query — returns available off-ramp connectors for a country and payment method, including fees, limits, and accepted assets.

​
Stellar

  • zeam_stellar_get_account — returns the full Horizon record for a Stellar account (balances, signers, thresholds).
  • zeam_stellar_get_account_transactions — returns paginated transactions for a Stellar account.
  • zeam_stellar_get_transaction — returns a transaction record by hash.
  • zeam_stellar_get_transaction_effects — returns effects (balance changes, trustline updates) for a transaction.
  • zeam_stellar_quote — returns a non-binding strict-receive path-payment quote.

​
Connect the API MCP

​
Warp

The Zeam API MCP server is available as a pre-configured integration in Warp. Add it from Settings → MCP Servers or ask Oz to connect it.

​
Other MCP clients

Add the API MCP server to your client’s configuration: 
{
  "mcpServers": {
    "zeam-api": {
      "url": "https://mcp.zeam.app/sse",
      "headers": {
        "Authorization": "Bearer $ZEAM_MCP_TOKEN"
      }
    }
  }
}
Contact [email protected] to obtain MCP access credentials.

​
Example workflows

​
Discover payment corridors

Ask your AI agent:
“What connectors are available for bank transfers to Zimbabwe?”
The agent calls zeam_connect_query with countryISO: "ZW" and method: "BANK_TRANSFER" and returns available connectors with fees, limits, and supported assets.

​
Inspect a transaction

“Show me the effects of transaction abc123…”
The agent calls zeam_stellar_get_transaction to fetch the transaction record, then zeam_stellar_get_transaction_effects to list balance changes and trustline updates.

​
Browse beneficiaries

“List all mobile money beneficiaries for association X”
The agent calls zeam_list_beneficiaries with the association ID and payment_method: "MOBILE_MONEY" filter.

​
Security

The API MCP server authenticates via bearer token and respects the same scopes and permissions as the REST API. The zeam_whoami tool returns your principal identity and the scopes your token was issued with. The documentation MCP server is public and read-only — it only exposes published content.
MCP tokens carry the same access as API tokens. Store them securely and never commit them to source control.