Connect an AI assistant with MCP

What it is

Binary's MCP server connects your workspace to Claude, Claude Code, Codex, Cursor, VS Code, ChatGPT or any other assistant that supports MCP. The assistant reads your live candidates, stages and analytics, and makes changes back in Binary.

Connect

1. Request access. An admin goes to Settings → the Integrations tab → the "MCP server" row → "Request access". The Binary team turns MCP on for your workspace.
2. Add Binary to your assistant. Follow the steps for your assistant below. You'll need the Binary server address: https://api.binary.so/mcp.
3. Sign in and allow. When your browser opens, sign in to Binary, choose the workspace, and click "Allow access".

Each teammate connects their own assistant. The connection acts as the person who allowed it.

Claude

Claude app, claude.ai or Claude Code on desktop:

1. Go to Customize → Connectors.
2. Click "+" → "Add custom connector".
3. Name it Binary, paste https://api.binary.so/mcp, and click "Add".
4. Sign in to Binary when prompted.

Claude Code in the terminal:

1. Run this in your terminal:

   claude mcp add --transport http binary https://api.binary.so/mcp

2. Run /mcp in Claude Code and sign in.

On a Team or Enterprise plan, an owner adds Binary first in Organization settings → Connectors.

Codex

1. Open Codex and click your profile at the bottom left → Settings (or press ⌘ ,).
2. Search for Plugins and open it.
3. Click "Add" at the top right → "Add MCP server".
4. Name it Binary, paste https://api.binary.so/mcp, and save. Sign in when prompted.

Cursor

1. Open this link on the computer where Cursor is installed: Add Binary to Cursor.
2. Cursor opens and asks to install Binary. Confirm it.
3. Sign in to Binary when Cursor prompts you.

Any other assistant

Look for a setting called Connectors, Integrations or MCP servers, add a new one, and paste https://api.binary.so/mcp as its address.

What the MCP can do

• Screen candidates. Read a job's candidates in batches, including form answers, resumes, video transcripts and LinkedIn profiles. Grade them against your criteria and write the result into a field you can filter on.
• Answer questions about your pipeline. Counts, rates, time in stage and trends, per job or recruiter, plus the candidates or interviews behind any number.
• Act on candidates. Change stages one at a time or in bulk, add labels, add and edit comments, and write or edit interview feedback.
• Request feedback. Email teammates on a job to ask for their feedback on a candidate.
• Add and move candidates. Import people from resumes, a spreadsheet or another ATS, with their files. Anyone whose email is already on that job is skipped. Move a candidate to another job, or delete candidates.
• Manage jobs. Create a job and write its application form, set its stages, closing date and the messages candidates see, open, pause or close it, choose whether it shows on the careers page or LinkedIn, and add or remove teammates.
• Edit your careers page. Change the company description and the jobs pinned to the top. Admins only.
• Check usage. See your plan and how much of this month's usage is left.

The MCP can't message candidates, export a CSV, schedule interviews or set up automatic AI review. Do those in Binary.

Notes & limits

• A connection carries your own permissions. It can't reach a job or candidate you can't open yourself. Referrers can't connect.
• Changes are recorded as you. A stage change the assistant makes shows "via agent" next to your name in the activity feed.
• The assistant's own reasoning runs on your plan with that assistant, so screening doesn't use Binary AI credits. LinkedIn profile lookups do, and so does any automatic AI review that runs on candidates the assistant adds.
• To disconnect, remove Binary from your assistant. Leaving the workspace also ends the connection.
• Most assistants ask you to confirm a change before making it. Keep that confirmation on.