CazVid MCP server

The MCP server is a stateless remote server at https://mcp.cazvid.com/mcp. Point any MCP client at it (Claude Code, Claude.ai custom connectors, ChatGPT developer mode, Cursor, VS Code) and the agent gets fifteen tools that wrap CazVid's public Job Builder, Candidate Search, Webhooks, Job Search, and CRM APIs. The server holds no secrets: it forwards your CazVid API key to the upstream API, and all quota and plan enforcement happens upstream.

Provide your CazVid API key one of two ways. Both hit the same validation path; pick the one your client supports.

Authorization: Bearer cazvid_jb_...
x-api-key: cazvid_jb_...

claude mcp add --transport http cazvid https://mcp.cazvid.com/mcp \
  --header "Authorization: Bearer cazvid_jb_YOUR_KEY"

{
  "mcpServers": {
    "cazvid": {
      "url": "https://mcp.cazvid.com/mcp",
      "headers": { "Authorization": "Bearer cazvid_jb_YOUR_KEY" }
    }
  }
}

{
  "servers": {
    "cazvid": {
      "type": "http",
      "url": "https://mcp.cazvid.com/mcp",
      "headers": { "Authorization": "Bearer cazvid_jb_YOUR_KEY" }
    }
  }
}

https://mcp.cazvid.com/mcp/cazvid_jb_YOUR_KEY

Every family's tools are exposed as one flat list. preview_job and create_job cover job posting; search_candidates covers candidate search; list_webhook_endpoints covers webhooks; search_jobs covers job search; the nine crm_* tools cover the CRM; list_api_usage reports all five families' quotas.

create_job defaults to a reviewable draft and publishes only when you explicitly ask it to. Its idempotency key is derived from the request content, so retrying with identical arguments within 24 hours returns the already-created job instead of a duplicate. search_candidates is read-only and returns no contact details. list_webhook_endpoints is read-only and never returns signing secrets; endpoints are created, verified, rotated, and deleted in the CazVid app or the REST API. search_jobs is read-only and returns public job posts, each with an applyUrl and never any hiring-manager contact details. In the CRM, crm_upsert_contact de-duplicates by email or phone within the workspace, so a retry that carries one of those returns the existing contact rather than a duplicate (a name-only create has no de-duplication key, so retrying it can produce a second contact); crm_log_interaction is never de-duplicated, so do not blindly retry a call that may already have succeeded; and crm_delete_contact is a soft delete that archives the contact along with its interactions and list memberships.

The MCP server uses the same CazVid Developer API key and the same per-organization daily quotas as the REST APIs. There is nothing new to provision.

• Job Builder: 10 successful preview_job or create_job calls per organization per UTC day.
• Candidate Search: 100 search_candidates calls per organization per UTC day, plus a 20-per-minute burst limit.
• Webhooks: list_webhook_endpoints consumes no quota. The webhook family's cap is on event deliveries, not on this tool - up to 5,000 deliveries per organization per day.
• Job Search: 500 search_jobs calls per organization per UTC day, plus a 30-per-minute burst limit.
• CRM: 500 crm_* calls per organization per UTC day, plus a 30-per-minute burst limit. This is a separate quota from the other families, and every metered call counts, reads included. crm_upload_resume also consumes 1 of a separate resume-upload quota of 50 per API key per UTC day.
• list_api_usage consumes no quota and reports all five families' used, remaining, and reset times.
• All quotas reset at UTC midnight. A rate-limited tool call returns the reset time and points you at list_api_usage.
• Keys come from Profile > Developer API in the CazVid app. The job-search scope is free - any registered CazVid account can mint a key for it. The job-builder, candidate-search, and crm scopes require a Platinum, Diamond, or Enterprise plan, and webhooks require a Platinum plan or higher. One key can carry every scope your plan allows.

For the full request and response contracts, see the Job Builder API docs, the Candidate Search API docs, the Webhooks API docs, the Job Search API docs, and the CRM API docs.

Connecting and listing tools works without a key so connector setup never breaks. Calling a tool without a key does not error hard - it returns clear guidance on how to add your key.

• The handshake (initialize) and tools/list succeed with no key, so a client can complete setup and show the fifteen tools.
• A tool call made without a key returns a readable message explaining how to connect, not a protocol error.
• Once a key is supplied (header or path form), the same tool call runs against your organization's quota.