Neo N3 MCP documentation

Reference material for the MCP stdio server, authenticated HTTP transport, deterministic validation, and checked-in deployment assets.

Current baseline: Node.js 22 or newer, 25 MCP tools, three fixed resources, one parameterized block resource, and HTTP bound to 127.0.0.1 by default.

Guides

Getting started

Install the package, configure stdio or HTTP mode, and make the first read-only request.

API reference

Review registered tools, resources, generic contract handling, and HTTP security behavior.

Architecture

Understand the entrypoints, services, handlers, storage boundary, and request flow.

Testing

Separate deterministic unit and built-server checks from live RPC and stress suites.

Deployment

Use the production Compose file, bearer authentication, wallet persistence, and health checks.

Examples

See current MCP calls, generic contract flow, and authenticated HTTP commands.

Operating model

MCP stdio supports mainnet, testnet, or both.
HTTP requires one network and defaults to 127.0.0.1:3000.
A non-loopback HTTP host requires an API key of at least 32 bytes.
When a key is configured, every HTTP route except /live and /health requires a bearer token.
State-changing MCP tools require an explicit network and confirm as the JSON boolean true.
Remote RPC endpoints require HTTPS unless NEO_ALLOW_INSECURE_RPC=true is explicitly set.
Signed transaction fees are capped at 20 GAS by default, leaving headroom above Neo's 10 GAS native deployment minimum.
The production Compose definition persists /app/wallets and binds the host port to loopback by default.

Boundaries

Local metadata and contract-name resolution do not certify third-party deployments or protocol behavior. The repository also does not include a metrics collector, dashboard, alerting system, cloud manifest, or automated production rollout. Verify those concerns in the target environment.