ripio-community-mcp

Unofficial, community-built, not affiliated with Ripio. Read-only. Use at your own risk.

A local MCP server that lets AI assistants read your Ripio account (balances, activity, prices, limits, open orders and deposit addresses) using your own API key. It runs on your computer and only talks to api.ripio.com.

🇦🇷 Instrucciones en español: README.es.md

Why use this instead of Ripio's official MCP?

Ripio has an official remote MCP server. If it works for you, use it. This project exists for the cases it doesn't cover:

Neither can show card transactions, in-app buys/sells or bill payments: Ripio's public API doesn't expose them.

Tools

Deposit safety

A wrong network, a missing memo or one mistyped character can lose the funds, so deposits get extra layers:

1. Exact output. Addresses and memos come back exactly as Ripio sends them. The server never creates an address: if Ripio hasn't assigned one for a network yet, it tells you to start that deposit in the Ripio app.
2. Network rules. ripio_get_deposit_address returns no address until the network is clear. Along with the address, it names the networks where that same address credits the asset, and the ones that need a different address. Your EVM address is the same on every EVM network, but Ripio only credits each asset on some of them.
3. Verification by code. The assistant retypes what it reads, and a language model can, rarely, change a character. Before sending, paste the address you will actually use and ask to verify it: ripio_verify_deposit_address compares it character by character with your real addresses and flags near misses.
4. Network checksums. Most networks (EVM with mixed-case addresses, Tron, Bitcoin, XRP, Stellar…) have a checksum, so the sending wallet usually rejects a mistyped address. Solana addresses have none.

For large amounts, send a small test deposit first. These are Ripio app (Wallet) addresses; Ripio Trade uses different ones.

Pesos sent to your CVU are credited in the deposit currency set in your Ripio app profile: if that is a crypto, they are converted automatically. ripio_get_deposit_accounts reminds you of this.

Setup

1. Create a read-only API key in Ripio

The steps use the labels of Ripio's English interface. If yours is in Spanish, switch it in Profile → Preferences → Language, or follow README.es.md.

1. Open app.ripio.com, click your avatar (top right) → Profile → API tab → New key.
2. IP restriction: choose Specific IPs and add your public IP (recommended), or No restriction. Home connections often get a new public IP now and then; when that happens the server reports a 403 until you add the new IP to the key.
3. Name the key and keep the Read-only preset (Consult 9/9, Operate within Ripio 0/3, Withdrawals and addresses 0/2).
4. Confirm with your 2FA method and copy the API Key and Secret Key. The secret is shown only once.

Ripio's "Read-only" preset still lets an API key register bank accounts in your own name. This server never calls that endpoint.

2. Add it to your client

Claude Desktop (easiest). Download ripio-community-mcp.mcpb from the latest release. In Claude Desktop, go to Settings → Extensions → Advanced settings → Install Extension…, pick the file, and paste your API key and secret when asked. Claude Desktop keeps them in your system keychain. Then ask in a regular chat, for example "How much do I have on Ripio and in what?"

Claude Code

claude mcp add --env RIPIO_API_KEY=your-key --env RIPIO_API_SECRET=your-secret --transport stdio ripio -- npx -y ripio-community-mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "ripio": {
      "command": "npx",
      "args": ["-y", "ripio-community-mcp"],
      "env": { "RIPIO_API_KEY": "your-key", "RIPIO_API_SECRET": "your-secret" }
    }
  }
}

VS Code (.vscode/mcp.json, or MCP: Open User Configuration for all workspaces). VS Code asks for the key and secret once and stores them securely:

{
  "inputs": [
    { "type": "promptString", "id": "ripio-key", "description": "Ripio API key", "password": true },
    { "type": "promptString", "id": "ripio-secret", "description": "Ripio secret key", "password": true }
  ],
  "servers": {
    "ripio": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "ripio-community-mcp"],
      "env": { "RIPIO_API_KEY": "${input:ripio-key}", "RIPIO_API_SECRET": "${input:ripio-secret}" }
    }
  }
}

Zed (settings.json)

{
  "context_servers": {
    "ripio": {
      "command": "npx",
      "args": ["-y", "ripio-community-mcp"],
      "env": { "RIPIO_API_KEY": "your-key", "RIPIO_API_SECRET": "your-secret" }
    }
  }
}

Any other MCP client (Cline, Continue…): add a stdio server with command npx, arguments -y ripio-community-mcp, and the environment variables below. See your client's MCP documentation for where that goes. It is also listed in the official MCP Registry as io.github.ruizemanuel/ripio-community-mcp, so clients that install from the registry can find it there.

Windows: if the server doesn't start (for example, "Connection closed"), launch npx through cmd. In Claude Code, end the command with -- cmd /c npx -y ripio-community-mcp; in JSON configs, use "command": "cmd" and "args": ["/c", "npx", "-y", "ripio-community-mcp"].

Configuration

Security model