Jami

jami-mcp

The official Model Context Protocol server for JamiDev, the SDK for Jami's creator payouts. Connect it to Claude, Cursor, VS Code, Codex or any MCP client and your agent can create ETB checkouts, watch them settle, reconcile orders, preview and send payouts, debug webhooks, and read the Jami docs while it writes your integration. Payments are processed by ArifPay.

Built on the official jami-sdk, so every tool behaves exactly like the SDK and the REST API.

npx -y jami-mcp

Quick start

1. Get a token: Jami dashboard → JamiDev → Developer → API Tokens. Start with a sandbox org — its jamidev_test_… token moves no real money.
2. Add the server to your client (below), with the token as JAMI_TOKEN.
3. Ask: *"Charge buyer@example.com 1,237 birr for order #1042 on Telebirr, phone 251900000001, and wait for it."*

No token yet? The server still runs. The docs, withdrawal-quote and webhook tools work without one, so you can start building right away.

Claude Code

claude mcp add jami -e JAMI_TOKEN=jamidev_test_xxx -- npx -y jami-mcp

Claude Desktop · Cursor · Windsurf

Add to claude_desktop_config.json, ~/.cursor/mcp.json or ~/.codeium/windsurf/mcp_config.json:

{

"mcpServers": { "jami": { "command": "npx", "args": ["-y", "jami-mcp"], "env": { "JAMI_TOKEN": "jamidev_test_xxx" } } } }

VS Code

.vscode/mcp.json — VS Code prompts for the token and stores it securely:

{

"inputs": [ { "type": "promptString", "id": "jami-token", "description": "JamiDev API token", "password": true } ], "servers": { "jami": { "type": "stdio", "command": "npx", "args": ["-y", "jami-mcp"], "env": { "JAMI_TOKEN": "${input:jami-token}" } } } }

Codex

~/.codex/config.toml:

[mcp_servers.jami]

command = "npx" args = ["-y", "jami-mcp"] env = { JAMI_TOKEN = "jamidev_test_xxx" }

Tools

Every tool returns a readable markdown summary plus typed structuredContent. Pass response_format: "json" for the raw payload. Money is always integer santim, and every parameter that takes money ends in _minor: amount_minor: 15000 = 150.00 ETB.

Prompts: integrate_jami (build a full integration in your stack), go_live_checklist, debug_payment. Resource: jami://reference — fees, limits, sandbox numbers, failure codes and webhook rules in one page.

Safety

The defaults are set so an agent can't move money by accident.

• Withdrawals are off until you start the server with --enable-withdrawals (or JAMI_ENABLE_WITHDRAWALS=true). When they're on, clients that support elicitation ask you to confirm each payout, and every payout needs an idempotency_key, so a retry can never pay twice. Sandbox tokens are refused before any request is made.
• `--read-only` registers only the tools that read data. Use it for reporting agents.
• Live mode is announced. With a jamidev_live_ token, the server tells the agent that checkouts charge real buyers and to confirm first.
• Tokens stay in the environment. They never appear in tool output.

Options

--http                 Streamable HTTP on POST /mcp instead of stdio

--port HTTP port (default 3333) --host HTTP bind address (default 127.0.0.1) --read-only Only read tools --enable-withdrawals Register jami_create_withdrawal --base-url Override the API base (default https://jami.bio/api/jamidev) --docs-url Override the docs origin (default https://dev.jami.bio)

Remote (HTTP) mode

npx -y jami-mcp --http --port 3333

→ http://127.0.0.1:3333/mcp (health check: /healthz)

The HTTP server is stateless, so any number of clients can share one process. Without JAMI_TOKEN, each request authenticates with its own Authorization: Bearer jamidev_… header, which makes one deployment safe to share across teams. On loopback it rejects foreign Host headers (DNS-rebinding protection). In HTTP mode, jami_create_test_webhook never sends requests; it only returns the signed payload and a curl command.

Embedding

import { createJamiServer } from 'jami-mcp';

import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';

const server = createJamiServer({ token: process.env.JAMI_TOKEN, docsUrl: 'https://dev.jami.bio', readOnly: true, withdrawals: false }); await server.connect(new StdioServerTransport());

Development

npm install

npm test # in-memory MCP client against a mocked API npm run build npm run inspect # opens the MCP Inspector on dist/index.js

Full guide: dev.jami.bio/docs/mcp · Support: support@jami.bio

MIT © Jami