Connect Your AI Assistant to Equip

Equip has a remote MCP server at https://equip.co/api/v3/mcp/. Connect your AI coding assistant to it and ask questions in plain language, such as “which of my job openings have the most candidates waiting in screening?”. The server is read-only: your assistant can look things up, and nothing is ever written or changed. If your plan does not include it, contact support and we can switch it on for your organization. Until then the Developers page shows an upgrade prompt in place of Connect your AI assistant.

Get Your Organization’s API Key

Every request to the MCP server carries your organization’s API Key. An organization Owner or Admin generates it.

Open the Developers page

Go to Account → Developers.

Generate the key

Click Generate API Key and copy the key (eqp_...). It is shown only once; if you lose it, click Rotate API Key to get a new one.

Put the key in your shell

Add this line to your shell profile (~/.zshrc or ~/.bashrc) so it survives new terminals:

export EQUIP_MCP=eqp_your_api_key

The variable is named EQUIP_MCP on purpose. Claude Code blanks any variable whose name contains KEY, TOKEN or SECRET when it fills in a remote server’s headers, so a name like EQUIP_API_KEY would silently fail.

The API Key card on the Account Developers page, before a key exists, with the Generate API Key button — The API Key card on the Developers page

The key is one key for the whole organization, not a personal login, and it acts as the organization’s admin: an assistant holding it can read everything an admin can, across every opening. Share it only with people who may see all of that, and rotate it if it leaks.

Pick Your Client

Each client has its own setup page with a copy-ready snippet and a check that the connection works.

Claude Code

One claude mcp add command.

Codex

Three lines in ~/.codex/config.toml.

Gemini CLI

One entry in ~/.gemini/settings.json.

The same snippets, and the full list of tools, are on Account → Developers under Connect your AI assistant.

The Connect your AI assistant section on the Account Developers page, showing the server URL, tabs for Claude Code, Cursor, VS Code, Codex and curl with Claude Code selected, and the claude mcp add command ready to copy — Connect your AI assistant on the Developers page, one tab per client

Cursor and VS Code

Both read the key from your environment or prompt you for it, so the key is never written into a config file.

Cursor

Add this to .cursor/mcp.json in your project, or use the Add to Cursor link on the Developers page.

{
  "mcpServers": {
    "equip": {
      "url": "https://equip.co/api/v3/mcp/",
      "headers": {
        "Authorization": "Bearer ${env:EQUIP_MCP}"
      }
    }
  }
}

VS Code

Add this to .vscode/mcp.json. VS Code asks for the key the first time the server starts and stores it securely.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "equip-api-key",
      "description": "Equip API key (eqp_...)",
      "password": true
    }
  ],
  "servers": {
    "equip": {
      "type": "http",
      "url": "https://equip.co/api/v3/mcp/",
      "headers": {
        "Authorization": "Bearer ${input:equip-api-key}"
      }
    }
  }
}

What Your Assistant Can Read

The tools mirror what a recruiter sees in Equip, grouped by area.

Group	Example tools
Job openings	`list_job_openings`, `get_job_post_stage_counts`
Candidates and applications	`find_candidate`, `list_job_applications`
Assessments and results	`list_assessment_results`, `get_assessment_scores_for_applications`
Interviews	`list_ai_interviews`, `list_live_interviews`
Organization	`list_organization_members`, `get_ats_insight`

The full list is on Account → Developers under Connect your AI assistant. A few tools appear only when your plan includes the matching feature, such as ATS Insights.

Any Other MCP Client

Any client that speaks Streamable HTTP can connect. It sends JSON-RPC 2.0 requests as POST to https://equip.co/api/v3/mcp/ with the key in an Authorization: Bearer eqp_... header (an X-API-Key: eqp_... header also works). There is no SSE stream and no session: a GET or DELETE to the URL is refused. Check the connection from a terminal:

curl -X POST https://equip.co/api/v3/mcp/ \
  -H "Authorization: Bearer $EQUIP_MCP" \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Troubleshooting

401 Invalid API key: the key was mistyped or rotated, or EQUIP_MCP is not exported in this shell. Run echo $EQUIP_MCP to check.
403 “isn’t included in your plan”: your plan does not include the MCP server. See Compare Plans, or contact support to have it switched on for your organization.
No tools, or an empty list: restart the client after adding the server.

Claude Code - Add Equip to Claude Code with one command
Codex - Add Equip to Codex’s config.toml
Gemini CLI - Add Equip to Gemini CLI’s settings.json
API Integrations - The REST API behind the same key, for inviting candidates and pulling results

ATS

Assessments

AI Interviews

Candidate Experience

APIs, Integrations & MCP

Account & Billing

Connect Your AI Assistant to Equip

Get Your Organization’s API Key

Pick Your Client

Claude Code

Codex

Gemini CLI

Cursor and VS Code

What Your Assistant Can Read

Any Other MCP Client

​Get Your Organization’s API Key

​Pick Your Client

Claude Code

Codex

Gemini CLI

​Cursor and VS Code

​What Your Assistant Can Read

​Any Other MCP Client

​Related Resources

Get Your Organization’s API Key

Pick Your Client

Cursor and VS Code

What Your Assistant Can Read

Any Other MCP Client

Related Resources