How to add Bankless Onchain MCP Server to Claude Desktop

Structured on-chain data: contract state, ABIs, source code, event logs, and transaction history. Paste the config into ~/Library/Application Support/Claude/claude_desktop_config.json and restart Claude Desktop.

Last updated June 15, 2026 · 120★ · stdio · apikey · official

Claude Desktop config for Bankless Onchain MCP Server

npx -y @bankless/onchain-mcp

{
  "mcpServers": {
    "bankless-onchain-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@bankless/onchain-mcp"
      ],
      "env": {
        "BANKLESS_API_TOKEN": "<your-bankless-api-token>"
      }
    }
  }
}

Setup steps

1Open Claude Desktop → Settings → Developer → Edit Config (this opens ~/Library/Application Support/Claude/claude_desktop_config.json).
2Paste the Bankless Onchain MCP Server config below under the top-level "mcpServers" key.
3Fill in any placeholder secrets (API keys, paths) in the snippet.
4Save the file, then fully quit and reopen Claude Desktop.
5Open a chat and confirm Bankless Onchain MCP Server's tools appear under the 🔌 tools menu.

Before you start

Node.js (LTS recommended) with npx available
A Bankless API token — sign up and generate one via the Bankless API onchain-mcp docs (set as BANKLESS_API_TOKEN)

What Bankless Onchain MCP Server can do in Claude Desktop

read_contract

Read smart-contract state (call view/pure functions) across supported networks

get_proxy

Resolve the implementation address behind a proxy contract

get_abi

Fetch the ABI (Application Binary Interface) for a contract

get_source

Retrieve verified contract source code and metadata

get_events

Fetch event logs matching filter criteria (address, topics, block range)

build_event_topic

Compute the keccak event topic/signature hash from an event name and argument types

get_transaction_history

Retrieve transaction history for an address

get_transaction_info

Get detailed information about a specific transaction

Security

Read-only on-chain data access with no transaction signing, so no funds are at risk; keep BANKLESS_API_TOKEN in env. Mind the ~10 req/min rate limit to avoid throttling.

Bankless Onchain MCP Server + Claude Desktop FAQ

Where is the Claude Desktop config file?

Claude Desktop reads MCP servers from ~/Library/Application Support/Claude/claude_desktop_config.json. Paste the Bankless Onchain MCP Server config there under the "mcpServers" key and restart the client.

Is Bankless Onchain MCP Server safe to use with Claude Desktop?

Read-only on-chain data access with no transaction signing, so no funds are at risk; keep BANKLESS_API_TOKEN in env. Mind the ~10 req/min rate limit to avoid throttling.

Do I need an API key?

Yes. The server requires a BANKLESS_API_TOKEN from the Bankless API. All tools route through the Bankless API, so requests fail without a valid token.

Can it send transactions or sign anything?

No. It is strictly read-only — contract reads, ABIs/source, events, and transaction history. It never broadcasts or signs transactions.

Is this project still maintained?

The GitHub repo is marked as no longer receiving updates. The npm package still installs and runs, but don't expect new features or fixes.

View repo Full Bankless Onchain MCP Server page