
How to add Bankless Onchain MCP Server to Cursor
Structured on-chain data: contract state, ABIs, source code, event logs, and transaction history. Paste the config into ~/.cursor/mcp.json and restart Cursor.
Last updated June 15, 2026 · 120★ · stdio · apikey · official
Cursor 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 Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
- 2Paste the Bankless Onchain MCP Server config below into the "mcpServers" object.
- 3Fill in placeholder secrets, then save.
- 4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
- 5Ask Cursor to use one of Bankless Onchain MCP Server's tools to confirm it's connected.
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 Cursor
read_contractRead smart-contract state (call view/pure functions) across supported networks
get_proxyResolve the implementation address behind a proxy contract
get_abiFetch the ABI (Application Binary Interface) for a contract
get_sourceRetrieve verified contract source code and metadata
get_eventsFetch event logs matching filter criteria (address, topics, block range)
build_event_topicCompute the keccak event topic/signature hash from an event name and argument types
get_transaction_historyRetrieve transaction history for an address
get_transaction_infoGet 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 + Cursor FAQ
Where is the Cursor config file?
Cursor reads MCP servers from ~/.cursor/mcp.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 Cursor?
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.