Zooq's MCP server

What is MCP?

Model Context Protocol is Anthropic's open standard for letting AI clients (Claude, etc.) discover and call external tools at runtime. Instead of you writing API wrappers in your agent code, your agent reads a list of tools from an MCP server and calls them directly via JSON-RPC. Zooq exposes its data endpoints this way.

Why it's safe to install

Available tools

The full catalog — 52 endpoints across 9 categories, every one of them callable from your MCP client. Tool names follow the convention category_endpoint (e.g. profile_full, companies_info_v2, search_jobs).

Every tool costs the same per-call rate as its REST counterpart — check your live balance and per-call cost on /dash.

Install in Claude Desktop

Open ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows) and merge:

{
  "mcpServers": {
    "zooq": {
      "url": "https://zooq.dev/api/mcp",
      "headers": {
        "X-API-Key": "zq_..."
      }
    }
  }
}

Replace zq_... with your key from /dash. Restart Claude. The tools appear in the tools menu under "zooq".

Install in Cursor

Cursor settings → MCP → paste:

{
  "mcp": {
    "servers": {
      "zooq": {
        "url": "https://zooq.dev/api/mcp",
        "headers": { "X-API-Key": "zq_..." }
      }
    }
  }
}

Install in Codex

Edit ~/.codex/config.toml — append:

[mcp_servers.zooq]
url = "https://zooq.dev/api/mcp"
http_headers = { "X-API-Key" = "zq_..." }

Install in Hermes

Edit ~/.hermes/config.yaml — merge under mcp_servers:

mcp_servers:
  zooq:
    url: "https://zooq.dev/api/mcp"
    headers:
      X-API-Key: "zq_..."
    enabled: true

Install in Openclaw

Edit ~/.openclaw/openclaw.json — merge into the root object (or run openclaw mcp set zooq '<json>'):

{
  "mcp": {
    "servers": {
      "zooq": {
        "url": "https://zooq.dev/api/mcp",
        "headers": {
          "X-API-Key": "zq_..."
        }
      }
    }
  }
}

Usage examples

Once installed, your agent sees every tool listed above. Sample prompts and the tool the agent will pick:

• "Get me the full LinkedIn profile of satyanadella" → profile_full
• "What does Stripe's LinkedIn page say?" → companies_name_lookup then companies_info
• "Find 10 VPs of Engineering at SaaS companies in San Francisco" → search_people
• "Pull every open role at Microsoft" → companies_universal_name_to_id then search_jobs with companies filter
• "Map the headcount growth of company X over the last year" → companies_insights

Agents can chain tools natively — the MCP protocol exposes the full parameter schema so the model knows which ID to pass where.

Pricing

Every MCP tool call deducts credits live, same as the REST API. No monthly minimum, no surcharge for MCP. See /pricing for the credit pack and subscription tiers.

Troubleshooting

• Tools don't appear in client: restart the app fully (quit, don't just close). Verify your config JSON is valid.
• "Invalid API key": double-check you copied the full key from /dash (it starts with zq_).
• "Insufficient credits" / "Payment required": top up at /billing.
• "Hourly credit cap reached": default is 500/h. Email hello@zooq.dev to raise it.
• Tool returns no data: the upstream might be temporarily degraded — check /status. If 5xx, your credits are auto-refunded.