MCP setup

The MCP server lets an assistant read CrowdIntel directly — pull a wallet's stats, screen for edge, look up a cluster — without you writing a request. It is read-only: nothing it exposes can change state, place an order, or spend money.

Setup is one config block and a token. Everything on this page works on a free account.

Get a token

Mint an MCP token at Settings → API. It is free on every plan, no card. MCP tokens are prefixed cint_mcp_ and shown once at creation.

MCP tokens and REST API keys are different objects — a cint_api_ key will not authenticate against the MCP endpoint, and a cint_mcp_ token will not authenticate against /api/v1. Mint whichever the client needs.

The endpoint

https://mcp.crowdintel.xyz/mcp

• Transport: remote Streamable HTTP, stateless JSON mode.
• Auth: Authorization: Bearer cint_mcp_… on every request.
• Read-only. Nothing here mutates state.

Claude Desktop

Add this to claude_desktop_config.json and restart Claude:

{
"mcpServers": {
  "crowdintel": {
    "type": "http",
    "url": "https://mcp.crowdintel.xyz/mcp",
    "headers": {
      "Authorization": "Bearer cint_mcp_YOUR_TOKEN_HERE"
    }
  }
}
}

Claude Code

Register the server from the CLI:

claude mcp add --transport http crowdintel https://mcp.crowdintel.xyz/mcp \
--header "Authorization: Bearer cint_mcp_YOUR_TOKEN_HERE"

To share it with a repository instead, commit the same server definition as .mcp.json in the project root:

{
"mcpServers": {
  "crowdintel": {
    "type": "http",
    "url": "https://mcp.crowdintel.xyz/mcp",
    "headers": {
      "Authorization": "Bearer cint_mcp_YOUR_TOKEN_HERE"
    }
  }
}
}

Cursor

Edit ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:

{
"mcpServers": {
  "crowdintel": {
    "url": "https://mcp.crowdintel.xyz/mcp",
    "headers": {
      "Authorization": "Bearer cint_mcp_YOUR_TOKEN_HERE"
    }
  }
}
}

Other clients

Zed takes the same URL under context_servers in its settings.json, with "source": "custom". Clients that cannot speak Streamable HTTP directly — older Claude Desktop builds among them — can bridge it:

{
"mcpServers": {
  "crowdintel": {
    "command": "npx",
    "args": ["-y", "mcp-remote", "https://mcp.crowdintel.xyz/mcp",
             "--header", "Authorization: Bearer cint_mcp_YOUR_TOKEN_HERE"]
  }
}
}

What the assistant can read

Tools appear automatically once the client connects. They group like this:

Wallets

Markets

Alpha discovery

Cohorts, clusters and investigations

Ask in plain language — "screen for human wallets with positive EV lower bound over at least 200 resolved bets", "what does the funding graph around this address look like", "which cohort does this wallet clear the floor for" — and the client picks the tool.

Limits

Daily call caps by plan:

There is also an hourly ceiling of 1,000 calls per token. No plan is denied access to any tool — the cap is the only wall, and every tool answers on a free token.

If you are building something that reads on a schedule rather than in conversation, use the REST API instead. It is the same data with a much higher ceiling, and it does not spend an assistant's turn.

Next

• API overview — the REST surface behind the same data.
• Quickstart — key to first response in about five minutes.