Neo N3 MCP Server

MCP server and HTTP API for Neo N3 and Neo X blockchain integration

Remote serverstreamable-httpTypeScript

What is the Neo N3 MCP MCP server?

Neo n3 mcp mcp server lets Claude, Cursor and other MCP clients work with Neo N3 MCP directly. MCP server and HTTP API for Neo N3 and Neo X blockchain integration.

What Neo N3 MCP does

@r3e/neo-mcp is an MCP server for Neo N3 blockchain queries and controlled, auditable transaction submission. It ships three entrypoints:

Installing the neo n3 mcp mcp server

The server is distributed via npm as @r3e/neo-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 8 environment variables: NEO_NETWORK, NEO_TESTNET_RPC, LOG_LEVEL, NEO_ENABLE_WRITES, NEO_SIGNER_WIF_FILE, NEO_WRITE_STATE_DIR, NEO_MCP_REQUEST_STATE_KEY, HTTP_WRITE_APPROVAL_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Neo N3 MCP sits in that group. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This is a hosted server — you point your client at an endpoint rather than running a local process, so there is nothing to keep updated on your machine.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Maintained by r3e-network, written in TypeScript.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the neo n3 mcp mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

How to install the Neo N3 MCP MCP server

{
  "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"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
NEO_NETWORKConfiguration value read at startup.Optional
NEO_TESTNET_RPCConfiguration value read at startup.Optional
LOG_LEVELConfiguration value read at startup.Optional
NEO_ENABLE_WRITESConfiguration value read at startup.Optional
NEO_SIGNER_WIF_FILEConfiguration value read at startup.Optional
NEO_WRITE_STATE_DIRFilesystem location the server is allowed to use.Optional
NEO_MCP_REQUEST_STATE_KEYCredential the server authenticates with.Yes
HTTP_WRITE_APPROVAL_API_KEYCredential the server authenticates with.Yes

Frequently asked questions

It connects Neo N3 MCP to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Neo N3 MCP directly.