Labsco
MCP SERVER

Algorand

by GoPlausible

Build, sign and submit Algorand transactions from a wallet the server holds the key for, and read the chain back — accounts, assets, applications, boxes — through algod and indexer.

Wallets, Signing & Transaction ExecutionVerified
Summary
One server covers the whole Algorand round trip: construct a transaction, sign it with a key it owns, submit it, then read the result back.

The wallet tools are what separate this from an API wrapper — the server holds the signing key and never returns the mnemonic, so an agent can go from make_payment_txn to send_raw_transaction without a human pasting a signature. That also makes part of the surface financially live: make_http_request_with_x402 pays for the endpoint it calls, and alpha_cancel_order refunds tokens plus ~0.957 ALGO of collateral. Of the 119 tools, a large block is third-party — Tinyman, Haystack, Pera, NFD and Alpha Arcade each get their own set — so a reader who wants algod and indexer reads carries the rest in context alongside them.

What it is

A server over Algorand's algod and indexer APIs with a local agent wallet attached, 119 tools spanning key handling, transaction construction, simulation, chain queries and several third-party Algorand services.

What you get
  • A wallet the server signs with: wallet_add_account stores an account under a nickname and keeps the mnemonic internally, wallet_switch_account picks the active signer, wallet_sign_transaction and wallet_sign_transaction_group sign with it and assign the group ID
  • The transaction constructors as a family — make_payment_txn, make_asset_create_txn, make_asset_transfer_txn, make_app_call_txn and the rest — with assign_group_id, encode_unsigned_transaction and send_raw_transaction to get them on chain
  • Two simulation paths before submission: simulate_transactions takes a full SimulateRequest config with execTraceConfig and extraOpcodeBudget, simulate_raw_transactions takes base64 bytes you already hold
  • Algod and indexer reads side by side: account, asset and application state, application boxes, pending transactions and node status, plus indexer search over accounts, assets, applications and transaction history
  • Key and encoding conversions: mnemonic to secret key or master derivation key and back, address encode, decode and validate, msgpack encode and decode, compile_teal and disassemble_teal
  • Third-party Algorand services under the same server: NFD name records, Tinyman pool and swap quotes, Haystack routed swaps across Tinyman V2, Pact and Folks, Pera verification tiers, and Alpha Arcade prediction markets down to the orderbook
  • X402 paid endpoints handled end to end — x402_discover_payment_requirements reads the accepts array without paying, make_http_request_with_x402 builds and signs the payment group, bazaar_list and bazaar_search browse the catalog of paid resources
Requirements

An Algorand account the server can hold the key for, created through wallet_add_account, and a network value on every call. The paying tools spend real balance: make_http_request_with_x402 draws USDC or ALGO from the active wallet, and the alpha_ order tools place live orders. MIT licensed.

Setup effort

One command — npm install -g @goplausible/algorand-mcp