tempo

tempo-mcp is an MCP server that bridges AI agents with the Tempo blockchain to enable autonomous stablecoin payments. It supports a wide range of operations including single and batch payments, scheduled and concurrent transfers, memo-enabled payments for invoice reconciliation, gasless sponsored payments, and advanced token and policy management (whitelists, roles, and compliance checks). The server exposes commands through MCP, allowingClaude-like assistants to query balances, execute payments, manage approvals, and monitor on-chain activity while enforcing safety features such as spending limits, address allowlists, and rate limits.

To use tempo-mcp, configure it in your MCP client (for example Claude Desktop) with the tempo server entry. The server runs on Tempo testnet by default and expects a private key for a testnet wallet. You can request free testnet AlphaUSD tokens from the Tempo faucet. Once configured, you can ask the agent questions like "What's my balance?", or issue actions such as "Send 100 AlphaUSD to 0x...", "Process payroll from employees.csv", or "Swap 1000 AlphaUSD to BetaUSD". The MCP layer will handle signing, transaction construction, and on-chain submission, while logging an audit trail for reconciliation and compliance.

Prerequisites:\n- Node.js 20.0.0 or higher\n- npm, pnpm, or yarn\n- Access to Tempo testnet with AlphaUSD tokens (testnet faucet available)\n\nInstall steps:\n1) Install globally or run via npx (no global install):\nbash\nnpm install -g tempo-mcp\n# or run directly with npx (no installation)\nnpx tempo-mcp\n\n2) Prepare configuration: create a .env or supply TEMPO_PRIVATE_KEY via environment variable. A minimal example for Claude Desktop is provided in the README:\njson\n{\n \"mcpServers\": {\n \"tempo\": {\n \"command\": \"npx\",\n \"args\": [\"tempo-mcp\"],\n \"env\": { \"TEMPO_PRIVATE_KEY\": \"0xYOUR_PRIVATE_KEY\" }\n }\n }\n}\n\n3) Start the server:\nbash\nnpm start\n# or\nnpx tempo-mcp\n\n4) If using a client like Claude Desktop, add the server entry under your MCP configuration, pointing to the tempo server configuration from step 2. Ensure TEMPO_RPC_URL and TEMPO_CHAIN_ID (if overriding defaults) match your testnet settings.\n\nOptional: If you prefer manual setup, you can also install from source:\nbash\ngit clone https://github.com/arome3/tempo-mcp\ncd tempo-mcp\nnpm install\nnpm run build\n

Tips and reminders:\n- This MCP server operates on Tempo testnet; do not use real funds. Always test with the faucet tokens first.\n- Set TEMPO_PRIVATE_KEY to a testnet wallet key; never commit real keys.\n- You can configure TEMPO_RPC_URL and TEMPO_CHAIN_ID to point to alternate Tempo networks if needed.\n- The server supports milestone features such as batch payments, scheduled payments, sponsored (gasless) payments, and compliance tooling (whitelist policies, role management, and pre-transfer validation).\n- For troubleshooting, check the server logs for audit entries and transaction results; ensure your wallet has sufficient testnet funds for the operations you perform.\n- Ensure MCP client configuration aligns with the tempo-mcp version in use to avoid protocol version mismatches.