Juicebox MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Juicebox MCP Show me the top candidates from my 'Senior React Developer' search."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Juicebox MCP
A local MCP server that reads your Juicebox sourcing data into Claude — saved searches and their scored results — using your own logged-in Juicebox session.
Runs entirely on your machine. Your session never leaves it, and every call is made as you, on your own seat.
Reads cost no export credits. Everything the read tools return comes from the
same free surface the search-results page already renders. One tool writes, and
says so: jb_run_search creates a real saved search in your workspace.
Install
Option A — Desktop Extension (easiest)
Download juicebox-mcp.mcpb from
Releases, then double-click it,
or drag it into Claude Desktop → Settings → Extensions.
There is no API key to paste. After installing, do the one-time browser steps below.
Option B — from source
git clone https://github.com/jnot807/juicebox-mcp.git
cd juicebox-mcp
npm install # also downloads the Chromium build (see note)
npm run login # a real browser opens — sign in to Juicebox yourself
npm run check # proves the session works headlessThen register it with Claude Code:
claude mcp add -s user juicebox -- node "$(pwd)/server.js"-s user makes it available in every session; without it the registration is
scoped to whatever directory you happened to run it from.
The one-time browser download
This drives a real Chromium, and that binary is not part of node_modules —
it is a one-time download of roughly 500MB into a shared cache
(~/Library/Caches/ms-playwright on macOS).
npm install fetches it automatically via a postinstall step. Desktop Extension
users need to run it once by hand, because an extension bundles node_modules
but not that cache:
npx patchright install chromiumIf it is missing, the server tells you so in plain language rather than throwing a stack trace about a missing executable.
Signing in
Authentication is a real sign-in, not a key. npm run login opens a browser
window; sign in to Juicebox as you normally would. The session is then stored in
session/ (gitignored, chmod 600) and reused headlessly.
Sign in again whenever npm run check starts failing — sessions expire.
Related MCP server: JobSpy MCP Server
Tools
Tool | What it does |
| Saved searches on a project (id + name). |
| A search's ranked candidates — name, LinkedIn URL, title, company, location, |
| Size a filter set without running a search — the tuning primitive. |
| WRITES. Creates and runs a new search from a natural-language prompt, then returns its candidates. Leaves a saved search visible to your whole workspace — confirm before using it. |
experience[] is the only way to see past employers: the API payload carries
just the current one, so alumni of a target company are invisible without it.
Which project it reads by default
Nothing is hardcoded. At sign-in, a probe loads /projects, which redirects into
a project your seat can see, and that id is saved as defaultProjectId in
session/session-meta.json.
It is written once and then left alone. The redirect follows whichever project
the app most recently had open, so trusting it on every run would make a tool call
with no projectId read a different project than it did yesterday.
Resolution order:
JUICEBOX_PROJECT_ID(env — this is what the Desktop Extension's optional "default project" field sets)JUICEBOX_VALIDATOR_PROJECT(env — also pins the auth check to that project)defaultProjectIdinsession/session-meta.json, set by discovery
Every tool also takes an explicit projectId, which always wins.
Juicebox project ids are ~20-character keys like c5PheL2fANnX6uBQVUdo — the
/project/<id>/ part of a URL. If you pass a UUID, the server rejects it with an
explanation rather than silently navigating to a project that does not exist.
Two rules the tools carry
verdictFound: false→unknown, never a negative. "No evidence found" and "evidence says no" are different verdicts. Collapsing them scores a candidate down for a criterion nobody could actually check.Broad skill terms dilute ranking. Skills are OR-weighted; a population-wide term like "Account Management" on a customer-success search inflates the pool by roughly 3.4×. Drop the generic terms and promote the one hard requirement to a skill filter.
Running scripts while the server is up
You can't share the browser profile: session/profile/ is single-writer, and the
MCP server holds it whenever it is running. A second process trying to open it
fails the auth check — which reports itself as "session expired" and sends you
round in circles re-logging-in.
For diagnostics, build a fresh context from the checkpoint instead. No lock, same session:
const { chromium } = require('patchright');
const browser = await chromium.launch({ headless: true });
const context = await browser.newContext({ storageState: 'session/storage-state.json' });How it works, and the traps
The results page is server-rendered on first load, so /api/profiles/results only
fires on interaction. The client nudges the pager to make the app issue its own
request, then captures the response — which carries the whole ranked set, not just
the visible page.
Three things that will bite anyone editing client.js:
Never use
addInitScript. Patchright silently no-ops it as an anti-detection measure — no error, the script just never runs. Usepage.on('response').The API's
linkedin_urlis encrypted (hex:hex), as areprofiles[].urlandprofileDetails.id. Real URLs come from the rendered cards and are joined on normalisedfull_name— measured at 100% on a live search.The list blanks mid-pagination. A null pager reading means "still moving", not "failed". Gating anything on pager-change detection during a transition is how two earlier bugs happened.
When it breaks
This rides Juicebox's internal API. There is no stability contract, and it can change without notice.
npm run checkfails → session expired:npm run login.The server says Chromium is missing →
npx patchright install chromium.jb_get_resultsreturnssource: "dom-fallback"→ the API capture broke; you losematchRateand criteria. CheckRESULTS_PATHstill matches.jb_get_resultsreportsjoinedLinkedInUrls: 0→ the card markup changed; revisitharvestCards/rewindToFirstPage.Empty search list → the project page markup changed; see
listSavedSearches.
Requirements
Node.js 18 or newer
A Juicebox account you can sign into
~500MB free disk for the Chromium download
Licence
MIT. Not affiliated with or endorsed by Juicebox.
Available Tools
4 toolsjb_countA
Size a filter set WITHOUT running a search — the tuning primitive. Free and side-effect free, so permute filters and compare before committing to a run. The endpoint is VERIFIED DETERMINISTIC (same body, same count on repeat), which is what makes the comparisons below trustworthy.
queryInput is a PATCH, not a whole body. It is merged over a ~164-key template harvested live from a saved search, because a PARTIAL body does not error — it returns result:0, which reads exactly like "nobody matches your filters". Pass only the keys you want to change. Use searchId to choose which saved search supplies the template; the response echoes baseline (the unpatched count).
ALWAYS CHECK noEffect IN THE RESPONSE. Unrecognised keys and wrong value shapes are dropped SILENTLY, so an unchanged count means the key name is probably wrong, NOT that the filter does not matter. Measured example: coSizes (company headcount) is ignored in all eight shapes tried, including [{name:"51-200"}], ["51-200"], [{title,tag}] and [{min,max}]. Its real shape is still unknown — set the filter in the Juicebox UI and capture the request before trusting it.
SOME FILTERS EXPAND RATHER THAN RESTRICT, which is the opposite of the intuition and was measured on one search (baseline 1413): dropping industries gives 1387 and dropping coTags gives 1247 — REMOVING them SHRINKS the pool, so they act as OR-expanders and cannot be used to narrow onto a category. An unrecognised industry ("mining & metals") returns the same 1387 as an empty list. What actually restricts: skills (removing all four widened 1413 to 4526), yearsOfExp (20 gives 881), selectedLocs, and criteria. Note this REVISES the older claim that broad skill terms widen the pool — specific skills restrict hard, broad ones merely fail to restrict. The practical rule is unchanged: drop skill terms that describe the whole population, and promote the ONE hard requirement to a skill (e.g. "AI Agents", not prose about being AI-first).
Inputs: queryInput (required), searchId, projectId.
jb_get_resultsA
Pull a saved search's ranked candidates — up to ~500 in one call. Returns name, LinkedIn URL, title, company, location, a numeric matchRate (0-100, banded) and per-criterion verdicts. Costs NO export credits: this is the same free surface the results page renders.
READING THE RESULTS: at the top of a ranked list every candidate meets every criterion, so criteria-met count does NOT discriminate up there — use matchRate and depth. A criterion with verdictFound=false is reported as result "unknown": that means no evidence was found, NOT that the candidate fails it. Never treat an unknown as a negative.
If the search has never been executed, this errors — open it in the app and press "Run search" once.
Inputs: searchId (required), limit, projectId, minMatchRate.
jb_list_searchesA
List the saved searches on a Juicebox project (searchId + name). Saved searches are stable and re-runnable, so this is the entry point for pulling existing sourcing work. Defaults to the configured project.
Inputs: projectId.
jb_run_searchA
CREATE and RUN a new Juicebox search from a natural-language prompt, then return its ranked candidates. This is the ONLY tool here that WRITES: it leaves a real saved search in the workspace, visible to the whole seat. Confirm with the user before calling it, and do not call it speculatively in a loop — each call is a persistent object someone has to look at.
THE PROMPT IS THE CONTROL SURFACE, and it beats filter tuning. Juicebox extracts filters from the prompt and does it well: "roughly $10M to $100M revenue" became revenueRanges ["$10m-$25m","$25m-$50m","$50m-$100m"], and "exclude enterprise megacaps and independent consultants" became an extra ranking criterion. Measured head-to-head against the best hand-tuned search on the same intent, the prompt-built one returned 42/44 usable candidates versus 22/30. So state the company shape, the geography, the seniority, the number the person must own, and what to EXCLUDE, in plain prose.
WRITE THE EXCLUSIONS EXPLICITLY. Two pollution categories dominate this market and both respond to being named: enterprise mega-caps (a "VP CS" at Microsoft or IBM owns a structurally different job) and independent consultants / fractional advisors / founders of CS consultancies.
DO NOT tune for a small pool. Pool size and top-of-list quality are uncorrelated — the better of two measured searches had 3.4x the pool. Tune for ranking, not reach.
matchRate is NOT comparable ACROSS searches: it is scored against each search's own criteria, so a stricter criteria set produces LOWER scores on BETTER people. Only the ordering within one search means anything.
Inputs: prompt (required), need, projectId.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: list saved searches, fetch ranked results, tune filter counts, and create/run a new search. No two tools overlap in function, making misselection unlikely.
All tools follow the consistent pattern of 'jb_' prefix + verb_noun (list_searches, get_results, run_search) with count as a concise verb. This is predictable and uniform.
Four tools is well-scoped for a talent sourcing server. Each tool earns its place and covers the core workflow without redundancy or bloat.
The surface covers the essential lifecycle: listing existing searches, retrieving results, tuning filters without execution, and creating new searches. Minor gaps like deleting or updating saved searches exist but are not critical for the primary use case.
Maintenance
Related MCP Connectors
AI resume triage for recruiters. Query your candidate pool from Claude or ChatGPT.
JobDiva MCP server for ChatGPT, Claude and any AI agent: search candidates, find candidate, search jobs, add candidate note, add candidates to hotlist, create submittal and create candidate in your own JobDiva account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to JobDiva yourself; Cotlet does not store your password and you need no JobDiva API key. About the official JobDiva API: JobDiva has a REST API with public Swagger docs, 759 paths across two versions, but it only works with a client ID that JobDiva provides, and JobDiva has no official MCP server (checked 23 Oct 2026). The API has no webhooks, so changes have to be polled, and updates and deletes are POST calls. Setup and FAQ: https://cotlet.dev/integrations/jobdiva-api-mcp-server
Bullhorn MCP server for ChatGPT, Claude and any AI agent: search candidates, find matching candidates for a job, add candidate note, submit candidates to a job, update submission status and list job submissions in your own Bullhorn account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Bullhorn yourself; Cotlet does not store your password and you need no Bullhorn API key. About the official Bullhorn API: Bullhorn has a REST API, but it is sold as a paid partner contract to technology vendors, not as a key for a recruiter or an agency (checked 23 Oct 2026). Bullhorn does not allow middleware or connector companies to build on it and has no official MCP server. Setup and FAQ: https://cotlet.dev/integrations/bullhorn-api-mcp-server
JobAdder MCP server for ChatGPT, Claude and any AI agent: search candidates, get candidate, list job applications, rate application, update application status, add candidate note, create candidate and create task in your own JobAdder account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to JobAdder yourself; Cotlet does not store your password and you need no JobAdder API key. About the official JobAdder API: JobAdder has a REST API, but not for every account (checked 22 Oct 2026). Access goes through JobAdder's API Partner terms, its pricing page lists API access on Essential and Pro and not on Lite, and there is no official MCP server. Setup and FAQ: https://cotlet.dev/integrations/jobadder-api-mcp-server
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables Claude to perform actions on X, LinkedIn, and Reddit via a Chrome extension, such as connecting with recruiters, finding threads, and replying to posts.361MIT
- AlicenseNot gradedqualityCmaintenanceEnables job search and scraping across multiple job boards (LinkedIn, Indeed, Glassdoor, etc.) with advanced filtering, directly from Claude Desktop or other MCP clients.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude AI to interact with LinkedIn through browser automation, including profile reading, people and job search, company research, post publishing, and profile editing.MIT
- AlicenseNot gradedqualityDmaintenanceEnables searching and evaluating job postings from LinkedIn and freehire.me directly through Claude Desktop. Provides tools to search jobs, fetch full posting details, and assess candidate fit using eligibility scans and a scoring rubric.MIT