Last Updated: October 1, 2026
Yativo has three Model Context Protocol (MCP) servers. Pick the one that matches what your AI assistant needs to do. Full guide: AI and MCP servers.
| Docs MCP | Fiat MCP | Agentic Wallet MCP (crypto) | |
|---|---|---|---|
| What it does | Searches and cites the Yativo docs | Checks balances, deposits, payouts, beneficiaries and payout methods; quotes and sends payouts | Checks an agentic wallet's balance, sends crypto payments and pays for x402 APIs |
| Acts on | Public docs only (read-only) | Your Yativo Fiat business account | One agentic wallet, within its connector's spending limits |
| Moves money | No | Yes. You approve each payout | Yes, within the connector's spending limits |
| Connect with | https://docs.yativo.com/mcp |
https://api.yativo.com/mcp |
npx @yativo/mcp-server (runs locally) |
| Sign in with | Nothing | OAuth sign-in (recommended for claude.ai, Claude Desktop and laptops) or an API key (X-Api-Key and X-Api-Secret, only from IPs on the key's whitelist) |
A connector key (yac_...) |
| Limits | None | 60 requests per minute. Production only for now | The connector's spending limits |
| Guide | docs.yativo.com/yativo/mcp | docs.yativo.com/yativo-fiat/mcp-server | docs.yativo.com/sdks/mcp |
💡 Start with the Docs MCP while you build. It needs no credentials and answers from the current docs instead of your assistant's training data.
Read-only, no API key. Your assistant can search the Fiat and Crypto docs, open the right page and cite it.
Claude Code
claude mcp add --transport http yativo-docs <https://docs.yativo.com/mcp>
Claude Desktop and claude.ai: go to Settings → Connectors → Add custom connector and enter https://docs.yativo.com/mcp.
Cursor: add to mcp.json, then reload Cursor:
{
"mcpServers": {
"yativo-docs": {
"url": "<https://docs.yativo.com/mcp>"
}
}
}
Works with your Yativo Fiat business account. Payouts follow a quote → confirm → send flow, and your MCP client asks you to approve each payout. See Fiat MCP server, or the published guide.
⚠️ API keys only work from the IPs on the key's whitelist, including for MCP. Laptops and home connections usually don't have a fixed IP, so use OAuth sign-in for desktop assistants.
Runs locally with npx @yativo/mcp-server and uses a connector key (yac_...). It works on one agentic wallet, within that connector's spending limits. See the published guide.