Algorand

Algorand is a carbon-negative, pure proof-of-stake Layer 1 blockchain with instant finality, low fees, and built-in support for smart contracts (AVM), standard assets (ASAs), and atomic transactions.

- Agent wallet — mnemonics stored in a local SQLite database, used by the MCP server to sign on the agent's behalf (mnemonics never returned in tool responses)
- Wallet accounts with human-readable nicknames
- Account creation, key management, and rekeying
- Transaction building, signing, and submission (payments, assets, applications, key registration)
- Atomic transaction groups
- TEAL compilation and disassembly
- Full Algod and Indexer API access
- NFDomains (NFD) name service integration
- x402 HTTP micropayments — automatic discovery and one-call paid requests using the active wallet (USDC/ALGO)
- AP2 tooling for Algorand
- Tinyman AMM integration (pools, swaps, liquidity)
- Haystack Router DEX aggregation (best-price swaps across Tinyman, Pact, Folks)
- Alpha Arcade prediction market trading (browse markets, orderbooks, limit/market orders, positions, claims)
- ARC-26 URI and QR code generation
- Algorand knowledge base with full developer documentation taxonomy
- Per-tool-call network selection (mainnet, testnet, localnet) and pagination

npm install -g @goplausible/algorand-mcp

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

The server runs overstdio. There are three ways to invoke it — pick whichever suits your setup:

No environment variables are requiredfor standard use. Network selection, pagination, and node URLs are all handled dynamically per tool call.

npm install -g @goplausible/openclaw-algorand-plugin

Edit~/Library/Application Support/Claude/claude_desktop_config.json(macOS) or%APPDATA%\Claude\claude_desktop_config.json(Windows):

{ "name": "api_algod_get_account_info", "arguments": { "address": "ABC...", "network": "testnet" } }

If nonetworkis provided, tools default tomainnet.

API responses are automatically paginated. Every tool accepts an optionalitemsPerPageparameter (default: 10). Pass thepageTokenfrom a previous response to fetch the next page.

The agent wallet is a local SQLite database that the MCP server controls on the agent's behalf. The server holds the mnemonics and signs transactions for the agent — the agent never sees the mnemonics in any tool response.

Backward compatibility (silent migration from OS keychain)

Older installs of this MCP stored mnemonics in the OS keychain (@napi-rs/keyring). On first startup after upgrading, the server runs a one-shot, silent migration:

- For everyaccountsrow whosemnemoniccolumn isNULLor empty, it attempts to read the mnemonic from the OS keychain under the service namealgorand-mcpkeyed by the address.
- If found, the mnemonic is copied into the DB column.
- The original keychain entry is left in place as a redundant backup; nothing is deleted.

After this completes, the DB is the sole source of truth. The keychain is consulted only as a fallback if the DB still has aNULLmnemonic for an address (e.g., the keychain was unavailable during startup and became available later). All new accounts created after the upgrade are written directly to the DB and never touch the keychain.

Orphan handling (archive, not delete).If anaccountsrow exists but its mnemonic isn't in the keychainandisn't already in the DB (e.g., the user copiedwallet.dbto a new machine without also moving the keychain entries, restored from a partial backup, or installed in Docker where the keychain never existed), that row is unusable for signing. Rather than delete it, the server marks the row asarchived(UPDATE accounts SET archived = 1 WHERE mnemonic IS NULL OR mnemonic = ''). Archived rows:

- arehidden from the defaultwallet_list_accountsresponse
- never become the active account(the active-account index is clamped to the end of the remaining active list, or reset to0if no active accounts remain)
- keep theiroriginal nickname(a partial unique indexidx_active_nicknameenforces nickname uniqueness only among active rows, so a newwallet_add_accountcan reuse the same nickname for a fresh keypair)
- aresurfaced viawallet_list_accounts { archived: true }for forensics or future recovery

This MCP implements the Algorand flavor of x402, where payments are USDC (or native ALGO) transfers on Algorand. It exposes two tools that collapse the seven-step manual flow (probe → parse → opt-in check → build fee payer → build payment → group → sign → encode → header → retry) into a single tool call.

Historical / filtered queries against an Algorand Indexer instance. Use these for time-range scans, paginated searches, log retrieval, and creator/holder discovery — anything algod's current-state endpoints cannot answer.

Pera Wallet tools aremainnet only— the Pera public API does not support testnet or localnet.

Trade on-chain prediction markets (YES/NO outcomes) denominated in USDC. All prices and quantities use microunits (1,000,000 = $1.00 or 1 share). Read-only tools work without a wallet; trading tools require an active wallet account.

Optional env var:ALPHA_API_KEY— needed for reward market data.ALPHA_API_BASE_URL— custom API endpoint (default:https://platform.alphaarcade.com/api).

algorand-mcp/ ├── src/ # TypeScript source │ ├── index.ts # Server entry point │ ├── networkConfig.ts # Hardcoded network URLs and client factories │ ├── algorand-client.ts # Re-exports from networkConfig │ ├── env.ts # Legacy env shim (unused) │ ├── types.ts # Shared types (Zod schemas) │ ├── resources/ # MCP Resources │ │ ├── knowledge/ # Documentation taxonomy │ │ └── wallet/ # Wallet resources │ ├── tools/ # MCP Tools │ │ ├── commonParams.ts # Network + pagination schema fragments │ │ ├── walletManager.ts # Agent wallet (SQLite-backed) │ │ ├── accountManager.ts # Account operations │ │ ├── utilityManager.ts # Utility functions │ │ ├── algodManager.ts # TEAL compile, simulate, submit │ │ ├── arc26Manager.ts # ARC-26 URI generation │ │ ├── knowledgeManager.ts # Knowledge document access │ │ ├── transactionManager/ # Transaction building │ │ │ ├── accountTransactions.ts │ │ │ ├── assetTransactions.ts │ │ │ ├── appTransactions/ │ │ │ └── generalTransaction.ts │ │ └── apiManager/ # API integrations │ │ ├── algod/ # Algod API │ │ ├── indexer/ # Indexer API │ │ ├── nfd/ # NFDomains │ │ ├── tinyman/ # Tinyman AMM │ │ ├── hayrouter/ # Haystack Router DEX aggregator │ │ ├── pera/ # Pera Wallet verified assets │ │ └── alpha/ # Alpha Arcade prediction markets │ └── utils/ │ └── responseProcessor.ts # Pagination and formatting ├── tests/ # Test suite │ ├── helpers/ # Shared test utilities │ │ ├── mockFactories.ts # Mock algod/indexer/keychain factories │ │ ├── testConfig.ts # Category enable/disable logic │ │ ├── e2eSetup.ts # E2E account provisioning + invokeTool() │ │ └── testConstants.ts # Well-known testnet addresses and asset IDs │ ├── unit/ # 11 unit test suites (mocked, fast) │ ├── e2e/ # 11 E2E test suites (live testnet) │ │ ├── globalSetup.ts # Account provisioning + fund-check │ │ └── globalTeardown.ts # Cleanup │ └── jest.config.e2e.js # E2E-specific Jest config ├── dist/ # Compiled output ├── jest.config.js # Unit test Jest config ├── tsconfig.json # Production TypeScript config ├── tsconfig.test.json # Test TypeScript config └── package.json

All tool responses follow the MCP content format. API responses include automatic pagination when datasets exceeditemsPerPage(default 10):

{ "data": { ... }, "metadata": { "totalItems": 100, "itemsPerPage": 10, "currentPage": 1, "totalPages": 10, "hasNextPage": true, "pageToken": "eyJ..." } }

PasspageTokenfrom a previous response to fetch the next page. SetitemsPerPageon any tool call to control page size.

# Install dependencies npm install # Type-check npm run typecheck # Build npm run build # Clean build output npm run clean

npm test # Unit tests (fast, no network) npm run test:e2e # E2E tests (testnet, generates account + fund link) npm run test:all # Both