Neo N3 MCP Server is an MCP server that integrates AI assistants with the Neo N3 blockchain for querying on-chain data and managing auditable transaction submissions. Built with Node.js, it connects directly to Neo N3 mainnet or testnet RPC nodes to inspect block heights, account balances, and contract states. Blockchain developers, Web3 analysts, and system administrators use it to query account activity and automate blockchain interactions through language models. The server operates in a read-only mode by default to prevent unintended on-chain mutations. When write operations are explicitly enabled, the server enforces approval flows via an idempotency journal and cryptographic HMAC verification. Private keys are never accepted directly through client prompts, and transactions require an owner-only signer WIF file. The package provides three separate interfaces: standard input/output for local desktop clients, a stateless HTTP transport conforming to the MCP protocol, and a standalone REST API for custom integrations.
Category: Developer Tools & Code Intelligence
Tags: blockchain, cryptocurrency, neo, smart-contracts, web3
npm install -g @r3e/neo-mcp, or use npx -y @r3e/neo-mcp directly. 3. Open your Claude Desktop or Cursor configuration file (claude_desktop_config.json). 4. Add neo-n3 to your mcpServers object: json { "mcpServers": { "neo-n3": { "command": "npx", "args": ["-y", "@r3e/neo-mcp"], "env": { "NEO_NETWORK": "testnet", "NEO_TESTNET_RPC": "https://testnet1.neo.coz.io:443", "LOG_LEVEL": "info" } } } } 5. Save the configuration and restart your client to start interacting with the Neo N3 blockchain.Part of MCP Servers
You can run Neo N3 MCP Server using npx with the command npx -y @r3e/neo-mcp, or install it globally with npm install -g @r3e/neo-mcp. Node.js version 22 or higher is required. Once installed, configure the server in your MCP client by pointing the command execution to the package and setting necessary environment variables like NEO_NETWORK.
Neo N3 MCP Server allows assistants to query blockchain metrics, inspect smart contracts, fetch account balances, and submit signed transactions. Read operations are permitted by default, while write actions like token transfers require explicit configuration, local signer files, and approval flows to maintain operational security.
The server supports local MCP clients that interact over standard input and output, such as Claude Desktop and Cursor. It also offers a dedicated stateless HTTP transport conforming to the MCP specification for remote client implementations, alongside an independent REST API for custom non-MCP HTTP integrations.
Write actions are disabled by default. When enabled via the NEO_ENABLE_WRITES setting, the server requires an owner-only signer WIF file and an HMAC state key. Write requests return a unique intent fingerprint that must be reviewed and accepted before any signed transaction is broadcast to the Neo network.
Yes, Neo N3 MCP Server is an open-source project managed by R3E Network. The source code, documentation, and configuration options are publicly accessible in the official GitHub repository at https://github.com/r3e-network/neo-n3-mcp.