The DeFi Report - Sponsor Image The DeFi Report - Industry-leading crypto research trusted by finance pros. Friend & Sponsor Learn more
Bankless Content MCP

Bankless, inside your AIClaudeChatGPTCursor

Every article, episode, transcript, airdrop and profile we publish, accessible to anything that speaks MCP.

Generate your key How to wire it up

Already a member? Sign in

Premium members only GitHub
Claude
What it knows

Years of Bankless.

01

Articles & newsletters

Every Bankless post, by keyword or slug. Body included for premium tokens.

search_posts get_post list_recent_posts
02

Podcast transcripts

Full transcripts, speaker-mapped. Or grep them for a phrase and get the matching snippet back.

search_transcripts get_podcast_transcript
03

Airdrop Hunter

Active opportunities, their quests, on-chain criteria, networks.

list_airdrops get_airdrop
04

Profiles

People, projects and tokens that Bankless tracks.

search_profiles get_profile
Also in

Your editor. Or your terminal.

01

Right in Cursor.

Project context Cursor doesn't have, surfaced where you're writing code.

Cursor · Staker.sol
// Staker.sol
contract Staker {
    address public operator;
    mapping(address => uint256) public shares;

    function delegate(uint256 amount) external {
        // ...
    }
}
Chat
Who runs EigenLayer and what does Bankless say about their approach?
get_profile
{ "slug": "eigenlayer" }

EigenLayer is led by Sreeram Kannan. Bankless tracks it as a restaking protocol on Ethereum. The profile flags it as a "trust-as-a-service" primitive, with notes on slashing and AVS onboarding.

02

Or just cURL.

Plain HTTP POST, JSON-RPC 2.0 body, Bearer token. The shape every MCP client uses.

~/bankless · zsh
$ curl -X POST https://www.bankless.com/mcp \
-H 'Authorization: Bearer bls_mcp_xxxx' \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"list_recent_posts","arguments":{"tag":"podcast","limit":2}}}'
 
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"structuredContent": {
"results": [
{ "id": 1234, "title": "Why the Restaking Renaissance is Real", ... },
{ "id": 1233, "title": "Modular L2s with Polynya", ... }
],
"count": 2
},
"isError": false
}
}
Setup

Three steps. About a minute.

1

Generate a key.

From your account, premium subscribers only. We show the token once.

2

Drop it into your client.

Claude Desktop's claude_desktop_config.json validator only accepts stdio servers, so we wrap the HTTP endpoint with mcp-remote (needs Node 18+). Add to ~/Library/Application Support/Claude/claude_desktop_config.json alongside any existing top-level keys, then restart Claude Desktop.

{
  "mcpServers": {
    "bankless": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.bankless.com/mcp",
        "--header",
        "Authorization: Bearer YOUR_TOKEN"
      ]
    }
  }
}

First launch downloads mcp-remote; subsequent launches are instant.

Newer Claude Desktop beta that also accepts url?

Some recent builds will load this simpler stanza instead. If Claude Desktop shows "not a valid MCP server configuration" after a restart, your build doesn't accept it — fall back to the mcp-remote version above.

{
  "mcpServers": {
    "bankless": {
      "url": "https://www.bankless.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}
What about Settings › Connectors › Add custom connector?

That dialog accepts OAuth (Client ID + Secret) only, so it does not work for Bankless static Bearer tokens today. Use the config file above instead.

Cursor Settings › MCP › Edit Config. The same JSON also works for Continue, Windsurf, and other HTTP-aware MCP clients.

{
  "mcpServers": {
    "bankless": {
      "url": "https://www.bankless.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

OpenAI Codex CLI uses ~/.codex/config.toml. Wraps the HTTP server with mcp-remote via stdio (needs Node 18+):

[mcp_servers.bankless]
command = "npx"
args = ["-y", "mcp-remote", "https://www.bankless.com/mcp", "--header", "Authorization: Bearer YOUR_TOKEN"]
ChatGPT Connectors / Custom GPTs?

ChatGPT's Connectors feature (Plus, Pro, Enterprise) requires OAuth, the same limitation as Claude Desktop's custom-connector dialog. It does not yet work for Bankless static Bearer tokens. Use the Codex CLI snippet above for terminal-based work.

Smoke-test the endpoint directly, no client needed.

curl -X POST https://www.bankless.com/mcp \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
3

Ask anything.

Your client discovers the tools automatically. Try "Find recent Bankless podcasts about modular blockchains" or "Summarise the latest piece on restaking."

Generate your key Technical docs on GitHub
Search Bankless