MCP
Open Quake
Remote MCP endpoint available

Your recruitment stack, available to AI.

Connect Quake to the AI tools your team already uses. Search live recruitment data and run approved actions through one secure endpoint.

Connect your client
Delegated OAuth Dataset-scoped No API keys
$codex mcp add quake --url https://ai.quake.dev/mcp
$codex mcp login quake
Opening secure authorization…
Dataset  Quake Recruitment
Scopes   mcp:read, mcp:write
Connected to Quake MCP
01 / Get started

One endpoint.
Three steps.

Quake handles client registration and OAuth automatically. No client secret, token, or configuration file to manage.

Add the endpoint

Give your supported AI client the Quake MCP URL below.

Authorize access

Sign in to Quake, choose one Dataset, then review the requested permissions.

Start working

Ask your AI client to search candidates, jobs, contacts, clients, or installed actions.

https://ai.quake.dev/mcp
02 / Client guides

Connect where
you already work.

Choose your client. Every connection opens Quake in your browser for authentication and Dataset consent.

Claude web & desktop

Add a custom connector

Use Quake as a remote connector across Claude web, Desktop, and mobile.

  1. Open Customize → Connectors. For Team or Enterprise, an Owner first adds it under Organization settings.
  2. Choose Add custom connector, name it “Quake,” and enter the endpoint below.
  3. Leave advanced OAuth Client ID and Client Secret fields empty, then choose Add.
  4. Connect, sign in to Quake, choose a Dataset, review access, and select Allow.
https://ai.quake.dev/mcp
03 / Capabilities

Built for real
recruiting work.

Bring live operational context into conversations without exporting records, copying spreadsheets, or handing over broad credentials.

01 — SEARCH

Find recruitment records

List and inspect Candidates, Contacts, Recruitment Jobs, and Clients using your existing Dataset permissions.

02 — DISCOVER

Explore installed apps

Let your AI client find the right installed app and action for the job.

03 — EXECUTE

Run approved actions

Execute app actions with explicit write scope and your client’s normal confirmation flow.

04 — CONTROL

Keep access aligned

Role changes and connection revocation take effect immediately—without waiting for an old token to expire.

04 / Security

Your data stays inside your permission boundaries.

Every connection is tied to one user, one Dataset, and the permissions that user has right now. Quake never asks you to paste an API key into an AI client.

mcp:read

Connect and discover

Required to connect, search permitted records, and discover installed apps or actions.

mcp:write

Execute actions

Adds write-tool capability; the underlying Dataset and integration permissions still apply.

OAuth 2.0

Delegated, revocable access

Authorize in Quake, rotate refresh tokens automatically, and revoke individual connections from Settings → Security.

05 / FAQ

Good to know.

What is Quake MCP?

Quake MCP is a secure Model Context Protocol endpoint. It lets supported AI clients access recruitment records and approved Quake actions through a standard tool interface.

Which clients are supported?

Quake supports Claude, ChatGPT custom MCP apps, Codex CLI, and Claude Code. Each uses the same public endpoint and delegated OAuth flow.

Do I need an API key or OAuth client secret?

No. Quake registers supported clients automatically. Sign in through Quake, select a Dataset, and approve the requested scope.

What can an AI client access?

Only the selected Dataset and only the data and actions allowed by your current Quake role. Removing MCP or underlying resource permissions blocks access immediately.

Can I revoke a connection?

Yes. Open Quake and go to Settings → Security → MCP Connections. Revoking one connection leaves your other client and Dataset connections intact.

Ready when you are

Put Quake in the conversation.

Choose your client