algorand

The Algorand MCP Server exposes Algorand blockchain operations as MCP tools so AI agents and LLMs can interact with wallets, accounts, transactions, and Algorand-specific features without exposing secret material. It supports secure wallet management, account creation and rekeying, transaction building and signing, atomic transaction groups, TEAL tooling, and full access to Algod and Indexer APIs, along with Algorand-specific integrations like NFDomains, x402, AP2 tooling, Tinyman AMM, and URI/QR generation. Clients communicate via the MCP stdio protocol, enabling tool calls such as api_algod_get_account_info, api_algod_send_transaction, or ARC-26 URI generation, optionally specifying the network (mainnet, testnet, or localnet) per tool call. To use the server, run it via the standard MCP entry points (npx, global install, or node with the built dist), then direct clients to invoke the appropriate tools with the required parameters.

Prerequisites:

• Node.js v20 or later
• npm, pnpm, or yarn

Installation options:

1. From npm (recommended):

npm install -g @goplausible/algorand-mcp

2. From source:

git clone https://github.com/GoPlausible/algorand-mcp.git
cd algorand-mcp
npm install
npm run build

Usage notes:

• The server runs over stdio by default. You can invoke it with npx, a global install name, or a direct node invocation to the built dist/index.js file.
• No environment variables are required for standard use; network selection and pagination are handled per-tool via API parameters.

Tips and caveats:

• If you install the plugin for OpenClaw, Claude, or other clients, the Algorand MCP server will be detected automatically in various clients’ MCP configuration examples.
• You can select the target network (mainnet, testnet, localnet) for each tool call; Algod and Indexer URLs for mainnet/testnet are provided by AlgoNode.
• The wallet stores mnemonics in the OS keychain and metadata in an embedded SQLite database; private keys do not leave tool responses. Ensure your environment has appropriate permissions to access the OS keychain.
• When integrating with multiple tooling ecosystems (Claude, Cursor, Windsurf, VS Code, etc.), you can reuse the same MCP configuration by pointing clients at npx @goplausible/algorand-mcp or the installed global command.
• For production usage, consider setting up proper authentication around your tooling layer and monitoring tool invocation counts to enforce spending limits.