Precursor Security
MCP Setup

Add Precursor Intelligence
to your agent.

41 read-only tools over Streamable HTTP. Two minutes from API key to your first query, in Claude Code, Claude Desktop, Cursor, or any MCP-compatible client.

Step 01

Get an API key

  1. Sign up free. No card, no sales call.
  2. In the dashboard, open Settings, then API Keys, and mint a key. It looks like prec_live_... and is shown once, so copy it.
  3. Pass it in the Authorization: Bearer header. Keys are IP-allowlisted and can be revoked at any time.
Step 02

Add the server to your client

Claude CodeClaude DesktopCursorZedAny MCP-compatible client
Claude Code
claude mcp add --transport http precursor-intelligence \
  https://mcp.precursorintelligence.com \
  --header "Authorization: Bearer <YOUR_API_KEY>"
Claude Desktop
{
  "mcpServers": {
    "precursor-intelligence": {
      "type": "http",
      "url": "https://mcp.precursorintelligence.com",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
Cursor
{
  "mcpServers": {
    "precursor-intelligence": {
      "type": "http",
      "url": "https://mcp.precursorintelligence.com",
      "headers": {
        "Authorization": "Bearer ${env:PRECURSOR_API_KEY}"
      }
    }
  }
}
Any client (HTTP)
curl -s https://mcp.precursorintelligence.com \
  -H "Authorization: Bearer $PRECURSOR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"account_status","arguments":{}}}'

Zed and any other MCP-compatible client use the generic HTTP configuration above: point the client at the server URL and send your key as an Authorization: Bearer header. Replace <YOUR_API_KEY> with the key from Step 1. In Cursor, store it as the PRECURSOR_API_KEY environment variable so it stays out of your config file.

Step 03

Verify it works

The server speaks JSON-RPC 2.0 over the Streamable HTTP transport (spec 2025-06-18). The quickest check is the account_status tool: it is free, and it returns your credit balance and current rate-limit state, so a valid response confirms your key is working.

verify with curl
curl -s https://mcp.precursorintelligence.com \
  -H "Authorization: Bearer $PRECURSOR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"account_status","arguments":{}}}'

Good to know

Read-only
All 41 tools query intelligence. None write, change or scan anything.
60 requests per minute
Default per-key rate limit. Limit and remaining are returned on every call.
1 credit per tool call
Lightweight calls such as account_status are free.
Every request logged
Attributable to your organisation and key, for your own audit trail.

Mint a key and start querying

The free tier is enough to wire up your agent and ask your first real question.

Setup questions

How do I connect Claude Code to the Precursor Intelligence MCP server?

Run the Claude Code MCP add command with the HTTP transport, pointing at the server URL and passing your API key as an Authorization bearer header. The full command is on this page, and the key is minted in the dashboard under Settings, then API Keys.

Which MCP clients are supported?

Claude Code, Claude Desktop, Cursor and Zed are supported, along with any MCP-compatible client. Clients without a dedicated snippet use the generic HTTP configuration: point them at the server URL and send your key as an Authorization bearer header.

How do I check my MCP connection is working?

Call the account_status tool. It is free, does not consume a credit, and returns your credit balance and current rate-limit state, so a valid response confirms the key and transport are working.

Is there a rate limit on the MCP server?

Yes. Keys have a default limit of 60 requests per minute. Each tool call costs one credit, except lightweight calls such as account_status which are free. Every request is logged against your organisation and key.