Name: Fuse Network
Author: fuseio

LABSCO SUMMARY

Read Fuse for free, sign on your own terms

The split is the point. Aim an agent at the hosted URL and it can read balances, token prices, staking positions, and UserOperation history straight away, with nothing installed. The moment you want it to move value, you run the server yourself and you hold the key.

What it is

An MCP server for the Fuse blockchain. It layers three back-ends behind one tool interface: JSON-RPC for chain primitives, the Fusebox SDK for prices, staking, portfolios, and ERC-4337 smart accounts, and Fusebox REST for notification, wallet, trade, and explorer endpoints. Fuse hosts a read-only endpoint; anything that signs runs on your own instance.

What you get

Chain reads that need no key: fuse_get_balance, fuse_get_transaction, fuse_get_receipt, fuse_read_contract with the ABI auto-fetched from the explorer, fuse_get_token_metadata, fuse_get_gas_price, fuse_resolve_ens, and fuse_get_account_abstraction_info.
Wallet and market data through Fusebox: fuse_list_wallet_tokens, fuse_list_wallet_nfts, fuse_get_token_price, fuse_get_token_price_change, fuse_get_token_price_history, fuse_list_supported_tokens, fuse_get_staking_options, fuse_get_staked_tokens, fuse_get_trade_quote, and fuse_get_user_operations.
REST access for webhooks and address subscriptions, plus fuse_smart_wallet_authenticate, fuse_smart_wallet_get_actions, fuse_trade_indicative_price, fuse_trade_liquidity_sources, and fuse_trade_price_change_over_duration.
Signing from a self-hosted instance: fuse_send_native, fuse_send_erc20, fuse_write_contract which simulates first so revert reasons surface, fuse_deploy_contract, fuse_sign_message for EIP-191, fuse_sign_typed_data for EIP-712, and fuse_get_signer_address to see which key is loaded.
Smart-account operations as ERC-4337 UserOperations: fuse_smart_get_info, transfers and approvals in both a token and an NFT variant, fuse_smart_approve_and_call, fuse_smart_call_contract, fuse_smart_execute_batch, fuse_smart_swap_tokens, fuse_smart_stake_token, and fuse_smart_unstake_token.

Requirements

The hosted endpoint at https://mcp.fuse.io/mcp speaks Streamable HTTP and takes no auth, covering the read tools. Fusebox-backed reads need a Fusebox public API key, issued from a Fuse developer account, and the notification tools also need that account's secret key. Anything that signs requires your own instance, run via Docker or Node, with a wallet private key in its environment — Fuse deliberately runs the hosted one without one. A further setting turns on gasless UserOperations through the paymaster.

Setup effort

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

See installation options

USE CASES

01

Portfolio questions in conversation

Ask what an address holds, what it is worth now, and what is staked.

fuse_list_wallet_tokensfuse_list_wallet_nftsfuse_get_token_pricefuse_get_staked_tokens

02

Debugging a failed transaction

Pull the transaction and its receipt, then read the contract state and smart-account status behind it.

fuse_get_transactionfuse_get_receiptfuse_read_contractfuse_get_account_abstraction_info

03

Shipping a contract without leaving the client

Deploy from bytecode, ABI, and arguments, then call it — the write simulates first so reverts show up before broadcast.

fuse_get_signer_addressfuse_deploy_contractfuse_write_contract

04

Gasless transfers from a smart account

Move tokens or NFTs as ERC-4337 UserOperations, sponsored by the Fuse paymaster.

fuse_smart_get_infofuse_smart_execute_batch

05

Quoting a swap before taking it

Get an indicative price and the liquidity sources behind it, then execute from the smart account.

fuse_get_trade_quotefuse_trade_indicative_pricefuse_smart_swap_tokens

06

Signing a message without broadcasting

Produce an EIP-191 or EIP-712 signature for an off-chain flow.

fuse_sign_messagefuse_sign_typed_datafuse_get_signer_address

38 tools

Listed in project docs. Your client may show a different list.

fuse_get_balance

fuse_get_transaction

fuse_get_receipt

fuse_read_contract

fuse_get_token_metadata

fuse_get_gas_price

fuse_resolve_ens

fuse_get_account_abstraction_info

fuse_list_wallet_tokens

fuse_list_wallet_nfts

fuse_get_staking_options

fuse_get_staked_tokens

fuse_get_token_price

fuse_get_token_price_change

fuse_get_token_price_history

BEFORE YOU INSTALL

What to know first

Tools you get

38 tools named in the project's documentation.

Requires

A client that can reach a remote MCP server over HTTP

Optional

FUSEBOX_PUBLIC_API_KEY in your environment
FUSEBOX_SECRET_API_KEY in your environment
FUSE_PRIVATE_KEY in your environment

Where it runs

Of the 7 documented clients, 1 runs the server on your machine and 6 connect to a hosted endpoint.

INSTALLATION

Connect your client

Server setup

claude mcp add

Claude Code

TERMINAL

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

Hosted endpoint

ENDPOINT URL

https://mcp.fuse.io/mcp

Add this hosted endpoint to your MCP client.

MCP Clients

Cursor

CURSOR · JSON

{
  "mcpServers": {
    "fuse": {
      "url": "https://mcp.fuse.io/mcp"
    }
  }
}

~/.cursor/mcp.json (or Settings → MCP → Add new server)

Claude Desktop

CLAUDE DESKTOP · JSON

{
  "mcpServers": {
    "fuse": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.fuse.io/mcp"
      ]
    }
  }
}

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) · %APPDATA%\Claude\claude_desktop_config.json (Windows)

Cline

CLINE · JSON

{
  "mcpServers": {
    "fuse": {
      "url": "https://mcp.fuse.io/mcp",
      "type": "streamableHttp"
    }
  }
}

~/.cline/mcp_settings.json (or MCP sidebar → "Add Remote Server")

Roo Code

ROO CODE · JSON

{
  "mcpServers": {
    "fuse": {
      "url": "https://mcp.fuse.io/mcp",
      "type": "streamable-http"
    }
  }
}

MCP sidebar → "Add Remote Server", URL https://mcp.fuse.io/mcp

Zed

ZED · JSON

{
  "context_servers": {
    "fuse": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "mcp-remote",
          "https://mcp.fuse.io/mcp"
        ]
      }
    }
  }
}

~/.config/zed/settings.json

Any MCP client — local build

Get the code and build it: git clone https://github.com/fuseio/fuse-mcp-server.git, then cd fuse-mcp-server, npm install and npm run build

Add this block to a client that starts local servers, with the absolute path to dist/index.js in your clone and your own keys:

ANY MCP CLIENT — LOCAL BUILD · JSON

{
  "mcpServers": {
    "fuse": {
      "command": "node",
      "args": [
        "<YOUR_PATH_TO_FUSE_MCP_SERVER>/dist/index.js"
      ],
      "env": {
        "FUSEBOX_PUBLIC_API_KEY": "<YOUR_FUSEBOX_PUBLIC_API_KEY>",
        "FUSE_PRIVATE_KEY": "<YOUR_FUSE_PRIVATE_KEY>",
        "FUSE_USE_PAYMASTER": "true"
      }
    }
  }
}

The Notification API tools also need FUSEBOX_SECRET_API_KEY (your Fusebox secret key, sk_live_…); add it to this env block if you use them. The hosted endpoint needs no keys.

Fuse Network