Fuse Network

Installation

Hosted endpoint

Use the hosted Streamable HTTP endpoint for read-only access:

claude mcp add fuse --transport http https://mcp.fuse.io/mcp

For clients that require a local subprocess bridge, the Fuse docs show:

npx -y mcp-remote https://mcp.fuse.io/mcp

Self-hosted

Self-hosting is required for write tools, private-key signing, contract deployment, ERC-4337 UserOperations, and higher-rate-limit/API-key use.

Docker:

docker build -t fuse-mcp-server .
docker run --rm -p 3000:3000 -e MCP_TRANSPORT=http -e FUSEBOX_PUBLIC_API_KEY= -e FUSE_PRIVATE_KEY= -e FUSE_USE_PAYMASTER=true fuse-mcp-server

Docker Compose:

docker compose up -d

Node stdio mode from a checked-out source tree:

npm install
npm run build
FUSE_PRIVATE_KEY= node dist/index.js

Configuration

Hosted remote target: streamable-http:https://mcp.fuse.io/mcp with no authentication and no query parameters.

Documented runtime environment variables: MCP_TRANSPORT, MCP_HTTP_HOST, MCP_HTTP_PORT, MCP_HTTP_PATH, FUSE_NETWORK, FUSE_RPC_URL, FUSE_EXPLORER_URL, FUSE_ENTRYPOINT_ADDRESS, ENS_RPC_URL, FUSEBOX_PUBLIC_API_KEY, FUSEBOX_SECRET_API_KEY, FUSEBOX_BASE_URL, FUSEBOX_API_ORIGIN, FUSE_PRIVATE_KEY, and FUSE_USE_PAYMASTER.

The official docs link to https://github.com/fuseio/fuse-mcp-server, but that URL returned HTTP 404 during review, so no repository or local package target is asserted here.

Capabilities

The hosted endpoint provides read-only access to 35 tools, including Fuse balances, transaction details, receipts, read-only contract calls, token metadata, gas prices, ENS resolution when configured, account-abstraction information, Fusebox SDK reads, and REST API reads.

Self-hosted mode unlocks 50 tools, including EOA transfers, ERC-20 transfers, contract writes, contract deployment, EIP-191 and EIP-712 signing, ERC-4337 smart-account UserOperations, swaps, staking, NFT/token approvals, batch execution, and optional gasless execution via the Fuse paymaster.

Limitations and Security

The hosted endpoint is read-only, has no FUSE_PRIVATE_KEY, and write tools return an error directing users to self-host. Fusebox SDK reads and REST APIs require FUSEBOX_PUBLIC_API_KEY; Notification API tools require FUSEBOX_SECRET_API_KEY; smart-account write tools require both FUSE_PRIVATE_KEY and FUSEBOX_PUBLIC_API_KEY; ENS resolution requires ENS_RPC_URL.

A self-hosted instance is a hot-wallet signer. The Fuse docs advise restricting ingress, funding the signer EOA only with funds the operator is willing to risk, and preferring FUSE_USE_PAYMASTER=true so the smart wallet can transact without holding gas. Private keys are read from the server environment at startup and are not accepted as tool arguments.