MCP · Pequod

MCP

GET or POST https://api.pequod.app/mcp. Streamable HTTP, JSON-RPC 2.0. Protocol 2025-06-18; the server still speaks 2024-11-05. Claude, ChatGPT and Cursor connect with a Clerk login. The credit meter is the same as REST.

client

GET or POST https://api.pequod.app/mcp

Point Claude, ChatGPT or Cursor at that URL and click Connect. An unauthenticated call returns 401 with WWW-Authenticate pointing at /.well-known/oauth-protected-resource. The client opens a Clerk login and consent, then retries with the access token. Scripts can still send Authorization: Bearer pq_live_…. Preferred protocol is 2025-06-18; 2024-11-05 still works. A single JSON-RPC object per POST, not a batch.

Add to Claude Add to Cursor

Claude Skill — official prospecting playbook (credits, workflow, 402/409). After a Pequod update that adds or changes tools: on the Pequod connector, Disconnect, then Connect, then start a new chat. You do not need to log in again. Reinstalling the connector is never required.

tools

find_decision_maker
get_credits
submit_job
get_job
estimate_cost
push_to_sheets

Same limits, credit weights, and finder options as the REST route — targetPersona, targetPersonas, verify gates, identity, company filters. Lookups can take 45–60 seconds — give the client a long timeout. More than twenty domains go through submit_job kind=decision_makers; call estimate_cost before large runs.

idempotency

idempotency_key is optional on the tools. If you omit it, or it does not match the ledger charset, the server synthesizes one from the account, the tool name and the arguments, so a repeated call with the same args does not charge twice.

curl initialize

curl -X POST https://api.pequod.app/mcp \
  -H "Authorization: Bearer pq_live_…" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"docs","version":"0"}}}'

After initialize, call tools/list and tools/call. Tool results include the HTTP status of the underlying route. Notifications (no id) return 202 with an empty body.