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.
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.
- 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`.
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.
One command plus a key — claude mcp add fuse --transport http https://mcp.fuse.io/mcp, then supply credentials