Fuse Network

What is Fuse Network?

Fuse Network is a Model Context Protocol (MCP) server for the Fuse blockchain. It lets AI agents (such as Claude, Cursor, and Gemini) read on‑chain data, submit account‑abstracted transactions, deploy contracts, and operate Fusebox APIs through a single standard tool interface. It can be used via a free hosted read‑only endpoint or by self‑hosting an instance that provides full write capabilities.

How to use Fuse Network?

The hosted endpoint is available at https://mcp.fuse.io/mcp using the Streamable HTTP transport. Point your MCP‑compatible agent at that URL – no setup beyond adding the server to the agent’s configuration. To enable write tools (e.g. sending transactions, deploying contracts), you must self‑host the server via Docker or node dist/index.js, setting the required environment variables (FUSE_PRIVATE_KEY, FUSEBOX_PUBLIC_API_KEY, etc.).

Key features of Fuse Network

• 50 tools across five categories: RPC reads, SDK reads, REST APIs, EOA writes, and smart‑account writes.
• RPC reads work without any API key; all other categories require one or more environment‑configured keys.
• Self‑hosted instance offers full write access; hosted endpoint is read‑only.
• Supports ERC‑4337 smart‑account UserOps, including gasless transactions via the Fuse paymaster.
• Private keys are only read from the environment at startup and never accepted as tool arguments.

Use cases of Fuse Network

• Read Fuse blockchain balances, transactions, and contract state without an API key.
• Query token prices, staking options, portfolio data, and UserOp history through Fusebox SDK tools.
• Send native FUSE, transfer ERC‑20 tokens, execute arbitrary contract calls, and deploy contracts from an EOA.
• Build gasless user experiences by submitting ERC‑4337 UserOps through the Fuse paymaster.
• Interact with Fusebox REST APIs for notifications, smart wallet authentication, trades, and explorer queries.

FAQ from Fuse Network

How does the hosted endpoint differ from self‑hosting?

The hosted endpoint (https://mcp.fuse.io/mcp) is read‑only because it does not have a private key configured. Write tools return an actionable error pointing you to self‑hosting. Self‑hosted instances can perform all 50 tools, including transactions and contract deployment, because you control the private key.

What dependencies or runtime are required?

Self‑hosting requires Node.js (for direct execution) or Docker. Environment variables such as FUSE_PRIVATE_KEY, FUSEBOX_PUBLIC_API_KEY, and FUSEBOX_SECRET_API_KEY must be set. No special hardware is needed; the server can run on a typical Linux, macOS, or Windows machine.

Where do my data and transactions live?

The hosted endpoint reads public data from the Fuse blockchain and Fusebox APIs. Self‑hosted instances run locally on your infrastructure – all signing and transaction submission happens on your own server. The README advises treating the self‑hosted server as a hot‑wallet signer and locking down ingress.

What are the known limits of the hosted endpoint?

The hosted endpoint is rate‑limited for fair sharing and cannot execute any write tools. The Fusebox public key bundled there is also subject to rate limits. To perform writes or obtain higher rate limits, you must self‑host.

Which transports and authentication methods are supported?

The hosted endpoint uses Streamable HTTP (POST with optional SSE upgrade) and requires no authentication. Self‑hosted servers can run on stdio (for local subprocess clients) or HTTP (configurable via MCP_TRANSPORT). Authentication for self‑hosted instances is provided through environment‑configured API keys and the private key.