Neo N3 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_FILE | No | Log file path | ./logs/neo-mcp.log |
| LOG_LEVEL | No | Logging level (debug/info/warn/error) | info |
| WALLET_DIR | No | Wallet storage directory | ./wallets |
| NEO_NETWORK | No | Default network (mainnet/testnet) | testnet |
| NEO_MAINNET_RPC | No | Mainnet RPC endpoint | https://mainnet1.neo.coz.io:443 |
| NEO_TESTNET_RPC | No | Testnet RPC endpoint | https://testnet1.neo.coz.io:443 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_network_modeA | Get the active network mode and available Neo networks. |
| get_blockchain_infoA | Get blockchain height, validator info, and the active network. |
| get_block_countB | Get the block count and latest block height for the selected network. |
| get_balanceA | Get NEO, GAS, and NEP-17 balances for an address. |
| get_unclaimed_gasB | Get the amount of GAS claimable by an address. |
| get_nep17_transfersB | Get NEP-17 transfer history for an address. |
| get_nep11_balancesB | Get NEP-11 balances for an address. |
| get_nep11_transfersC | Get NEP-11 transfer history for an address. |
| list_famous_contractsB | List supported well-known contracts for the selected network. |
| get_contract_infoC | Get metadata and operations for a contract by known name, script hash, or Neo address. |
| get_contract_statusB | Check whether a contract is deployed and inspect its current on-chain status by known name, script hash, or Neo address. |
| get_walletA | Get sanitized metadata for a locally stored wallet by address. |
| get_blockC | Get block details by height or hash. |
| get_transactionB | Get transaction details by hash. |
| get_application_logA | Get the application log for a transaction hash. |
| wait_for_transactionC | Wait for a transaction to be confirmed on-chain. |
| invoke_contractB | Run a read-only smart contract invocation without signing or broadcasting a transaction. |
| estimate_transfer_feesB | Estimate network and system fees for a transfer. |
| estimate_invoke_feesC | Estimate network and system fees for a contract invocation by script hash or a generic contract reference. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| neo-network-status | Network status for the default configured Neo network. |
| neo-mainnet-status | Network status snapshot for Neo mainnet. |
| neo-testnet-status | Network status snapshot for Neo testnet. |
TDQS
Scored across 19 tools
Most tools target distinct resources, but get_balance and get_nep17_balances overlap since get_balance already includes NEP-17 balances. get_blockchain_info and get_network_mode also share active-network information, and get_contract_info vs get_contract_status could be confused without careful reading.
The naming is mostly consistent with clear get_* prefixes and snake_case verbs. Minor deviations exist with list_famous_contracts, wait_for_transaction, invoke_contract, and estimates, but they are still predictable and readable.
At 19 tools, the server sits in the heavier range and feels borderline for a focused toolkit. Each tool is individually reasonable, but the set could be tightened by consolidating overlapping query tools.
The server covers a solid range of read-only Neo N3 operations: balances, transfers, blocks, transactions, contracts, fees, and network info. However, there are notable gaps for a full blockchain MCP surface, such as sending transfers, claiming GAS, or performing signed contract invocations.