Mina MCP Server

Overview

The Mina Protocol organization's official MCP server exposes Mina blockchain tooling and developer workflows to AI assistants. An agent builder plugs it in to give a coding or onchain agent working context on the Mina zk-focused chain without hand-rolling its APIs. Early-stage repo; scope is still small.

Tool inventory — 31 tools, probed live 2026-10-15

• get_account — Get account information by public key from the live daemon (tutorial + live modes).
• get_staking_ledger — [tutorial] Get staking ledger entries from the archive database. Returns up to 100 accounts with their staking info. Tutorial mode only — requires a local archive DB.
• get_tracked_accounts — [infra] List all accounts tracked by the daemon wallet (tutorial mode only). These are the pre-funded test accounts available for transactions.
• get_block — Get a block by state hash or height. Defaults to a "lite" summary (header + transaction counts) that stays within the tool budget; use detail to pull paged transactions or the full block. In tutorial
• list_blocks — [tutorial] Archive-DB-backed list of blocks ordered by height descending. Tutorial mode only (live mode has no archive DB — use `get_archive_blocks` against the Archive-Node-API instead). Prefer `get_
• get_best_chain — Get the current best chain from the live daemon. Returns per-block headers + transaction counts (always within budget) — use get_block for a specific block's transactions. detail:"full" returns comple
• get_transaction — Look up a transaction by its hash in the archive database.
• search_transactions — Search user commands in the archive database by sender, receiver, and/or amount range.
• send_payment — Send a MINA payment between accounts (tutorial mode). Uses the daemon's wallet to sign.
• send_delegation — Delegate stake to a block producer (tutorial mode).
• get_transaction_status — Check the daemon's status for a submitted transaction (PENDING / INCLUDED / UNKNOWN). Pass the id returned by send_payment as `payment` (or a zkApp tx id as `zkappTransaction`) — exactly one. Use this
• get_mempool — List transactions currently pending in the daemon's mempool (not yet in a block), optionally filtered by `publicKey`. Each entry has top-level `from`/`to` (B62q… pubkeys) plus `amount`/`fee`/`nonce`/`
• get_sync_status — [infra] Get the sync status and daemon info. Returns the flat daemon status object directly — fields like `syncStatus`, `blockchainLength`, `stateHash`, `numAccounts`, `chainId`, `addrsAndPorts` are a
• get_genesis_constants — Get the network's genesis constants: coinbase reward, account-creation fee, slot/epoch timing, k (confirmations), and ledger depth. Use these to reason about fees, finality, and timing rather than har
• get_network_id — Get the daemon's network identifier (e.g. 'mina:mainnet', 'mina:devnet'). Use this to confirm which network the server is actually talking to before interpreting balances or submitting transactions.
• get_archive_stats — [infra][tutorial] Statistics from the local archive database: total blocks, commands, accounts, etc. Tutorial mode only — live/snapshot don't have an archive DB.
• query_archive_sql — [infra][tutorial+snapshot] Execute a read-only SQL query against the archive database. Only SELECT/WITH/EXPLAIN statements are allowed. Query timeout is 10 seconds. Not available in live mode (no arch
• get_archive_schema — [infra] Get the archive database table names and their columns. Useful for understanding what data is available for SQL queries.
• get_events — [tutorial+live] Get emitted events from a zkApp address via the Archive-Node-API. Events are state-change notifications emitted by zkApp account updates. Snapshot mode does not run an Archive-Node-API
• get_actions — [tutorial+live] Get dispatched actions from a zkApp address via the Archive-Node-API. Actions are reducer inputs that modify zkApp state. Snapshot mode does not run an Archive-Node-API and rejects thi
• get_archive_blocks — [tutorial+live] Get finalized blocks from the Archive-Node-API (height, creator, timestamp, coinbase). Prefer this for live mode (the archive node holds canonical history) over `get_best_chain` (daemo
• get_network_state — [tutorial+live] Get network state from the Archive-Node-API: max canonical and pending block heights. (Different from `get_sync_status` which queries the daemon, and from `describe_state` which aggreg
• faucet — [infra] Get a ready-to-use funded test account (tutorial mode only). Acquires a pre-funded account (1550 MINA), imports its key into the daemon, and unlocks it for signing. The account is reserved unt
• return_account — [infra] Release a test account back to the pool (tutorial mode only). Call this when you're done with an account obtained from faucet.
• reset_session — [infra] Release every test account currently held by this session back to the pool. Useful when you want to start fresh without disconnecting.
• freeze_reset — [admin] Pause the periodic chain-reset janitor for N minutes. Use before a human demo so the chain state stays stable; the freeze auto-expires after the duration. Pass 0 to clear the freeze.
• unfreeze_reset — [admin] Resume the periodic chain-reset janitor immediately, cancelling any active freeze.
• freeze_status — [admin] Show whether the chain-reset janitor is currently frozen and how much time remains.
• describe_state — [infra] Snapshot of the live network: sync, latest block, mempool size, accounts in use (server-wide and this session), reset-freeze status, plus suggested next-tool hints. Call this first to orient y
• list_examples — [infra] List curated example workflows (each is a sequence of tool calls). Filter by the current server mode by default; pass `all` to see every workflow regardless of mode.
• get_example — [infra] Get the full step list for a single named example workflow. Use list_examples first to discover names.

Answers a handshake

yes · 2026-10-15

Answers a call

yes — get_staking_ledger returned in 104 ms

Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.

Where Mina MCP Server fits

Related concepts: What Are Onchain Agents?, How Agents Use Wallets