Jd Intel Mcp

jd-intel

[MIT License] [Node.js 18+] [npm] [jd-intel downloads] [jd-intel-mcp downloads] [GitHub stars]

Stop pasting job descriptions into AI assistants. Let your AI fetch them directly.

Full text. Clean structure. Across nine major ATS. No copy-paste. No context loss.

Why this exists

Your AI assistant already knows a lot about you. Your resume is in its memory. Your target roles, your past projects, your background. Ready to help the moment you feed it a job description.

So you copy-paste.

A JD from one company. Another from the next. A half-dozen more from your target list. Half have broken HTML. Salary info dies in translation. Links get stripped. And for every role, the dance starts over.

You could wait for the job boards to ship their own MCPs. They'll get there eventually. On their timeline. Filtered through their priorities, not yours. Tied to their query abstractions.

jd-intel skips that wait. Raw JDs, fetched directly by your AI, on your terms. One level below the curated layer.

Try asking your AI:

"Find AI/ML engineering jobs posted this week." "What product designer roles are open at fintechs right now?" "Pull the staff PM roles posted in the last 7 days."

Done.

Why not just scrape?

Because scraping breaks where jd-intel doesn't:

• Full JDs when browsing fails. SPA-rendered boards, slow loads, auth walls, and geo-restrictions block a browser. They don't block a public API call.
• Structured data, not HTML soup. Salary, location type, department, and clean markdown, normalized across nine ATS.
• No keys, no browser. Public APIs only. Runs anywhere your AI does.
• One schema, every platform. Greenhouse, Lever, Ashby, SmartRecruiters, Teamtailor, Recruitee, Personio, Workable, Workday return the same shape.

What you can do with it

• Look up open roles at any company directly from your AI, no copy-paste
• Tailor your resume across ten roles in one conversation
• Rank openings by fit with your background
• Scan a whole sector: "Pull open roles at fintech companies posted this week"
• Research teams by reading their JDs in bulk

The toolkit fetches. Your AI thinks.

Install

Works with MCP-aware AI clients: Claude Desktop, Claude Code, Cursor, Windsurf, VS Code. ChatGPT, Gemini, and other non-MCP clients don't support this yet. They use different tool-calling systems. (We wish they did. The protocol works the same way regardless of which AI you talk to.)

Everything runs locally on your machine. That also means desktop only: mobile apps can't run a local MCP server, so jd-intel isn't available on phones or tablets.

Claude Desktop (one-file install, no terminal)

The simplest path. No Node.js, no terminal: Claude Desktop runs the server on its own bundled runtime.

1. Download the extension: jd-intel.mcpb.
2. In Claude Desktop, open Settings, then Extensions, then Advanced settings, and click Install Extension. Pick the file you downloaded.
3. Review the access summary, click Install, then start a new chat. The tools appear automatically.

Shortcuts: drag the .mcpb onto the Settings window, or double-click it when your system opens .mcpb files with Claude Desktop. The extension is open source and unsigned, so Claude Desktop shows an "unverified" notice. Choose Install Anyway.

Prefer the terminal, or on an older Claude Desktop? Install Node.js 18+, run npx jd-intel-mcp install, then reopen Claude Desktop. Or edit the config file directly, see Manual install.

Other clients (Claude Code, Cursor, Windsurf, VS Code)

One-file .mcpb install is a Claude Desktop feature; these clients run the same server via npx and need Node.js 18+.

Claude Code

claude mcp add jd-intel -- npx -y jd-intel-mcp

Cursor (Settings, then Tools & MCP, then New MCP Server, or edit ~/.cursor/mcp.json):

{  "mcpServers": {    "jd-intel": { "command": "npx", "args": ["-y", "jd-intel-mcp"] }  }}

Windsurf (Settings, then Tools, then Windsurf Settings, then Add Server, or View Raw Config to edit mcp_config.json). Use the same mcpServers block as Cursor, then press refresh.

VS Code (Copilot agent mode): run the MCP: Add Server command, or create .vscode/mcp.json. The key is servers and the type is stdio:

{  "servers": {    "jd-intel": { "type": "stdio", "command": "npx", "args": ["-y", "jd-intel-mcp"] }  }}

Confirm it's working

Start a new chat and ask: "What fintech companies are in your jd-intel registry?" If it lists companies, you're set. Then try the real thing: "Find senior PM roles open right now that I'd be a fit for."

Tools not appearing?

• Fully quit and reopen the client (quit, do not just close the window). Claude Desktop: system tray then Quit (Windows), or ⌘Q (macOS).
• For npx clients (Claude Code, Cursor, Windsurf, VS Code), run npx clear-npx-cache, then restart.
• Confirm node --version is 18 or newer for the npx paths. The one-click .mcpb does not need Node.

For developers

npm install jd-intel

import { fetchJobs } from 'jd-intel';
const jobs = await fetchJobs({  company: '<your-target-company>',  titleFilter: 'designer',  postedWithinDays: 14,  limit: 50,});

Results come back newest first by postedAt, undated last (order: 'board' keeps the ATS's own order). fetchJobs returns the page as an array. fetchJobsDetailed returns the same page plus total_matched, the number of matches before offset and limit, so you can tell a small board from a cut and page through the rest:

import { fetchJobsDetailed } from 'jd-intel';
const { jobs, total_matched } = await fetchJobsDetailed({  company: '<your-target-company>',  titleFilter: 'engineer',  limit: 20,  offset: 20, // second page});

The same result says how the company was resolved and which boards answered:

• match: registry (a known company, one adapter call), probe (not in the registry, every adapter asked) or workday_override (an explicit Workday config).
• company: { key, name } from the registry row on a registry match, null otherwise.
• boards: one entry per board that answered, { ats, slug, name, site, board_url, org_name, org_url, jobs_found, matched, selected, scan }. jobs_found counts the rows the board listed before any filter. Workday and SmartRecruiters filter their list before fetching details, so for them it is the list count, not the rows that came back (a lower bound when the list scan caps). matched is the rows left after filters and before offset and limit, so a board whose rows were all cut from the page still shows up. board_url is built from the slug. org_name and org_url are what the board states about itself, the organization name in the ATS response and the careers or company host its links point at, and they are null where the platform exposes nothing (Lever and Ashby expose neither); nothing is filled in from the slug or the registry name. A probe match is a slug match, not a confirmed identity: compare org_name and org_url with the company you meant, and open board_url when they are null, before treating the jobs as that company's.
• failed: adapters that threw during discovery, { ats, slug, name, code, message }, with code either rate_limited or ats_unreachable. When no board answered and a check failed, fetchJobs throws that error instead of returning [], so an outage never reads as "not found".
• total_before_filters: the sum of jobs_found. Zero matches with a positive total_before_filters means the company is hiring and nothing passed the filters, on every ATS.

detectAtsDetailed(company) returns { boards, failed }: registry rows first (source: 'registry', never probed), then every live probe that answered (source: 'probe'), in platform order; failed lists the probes that could not be checked, with the same codes. detectAts keeps returning [{ ats, slug }].

A call the library cannot make throws ArgumentError (code: 'invalid_args'): no company, an unknown ats, or a titleFilter or filter that does not compile as a regex. It is thrown before any request goes out.

CLI usage: npx jd-intel fetch <company-slug> --title-filter "engineer" --posted-within-days 14. Full filter reference below.

Each ATS request gives the server 10 seconds to start responding. A 429, a 5xx or a network error is retried up to three attempts with backoff (1s, 2s), honoring Retry-After when the ATS sends one, and at most 4 requests run at a time per host. A failure that outlasts the retries throws an AtsError whose code is rate_limited or ats_unreachable.

Node.js 18+. No API keys. No configuration.

Manual install (fallback)

If npx jd-intel-mcp install fails, edit the config directly.

Config file location:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{  "mcpServers": {    "jd-intel": {      "command": "npx",      "args": ["-y", "jd-intel-mcp"]    }  }}

Restart Claude Desktop.

Updating

• Claude Desktop extension (.mcpb): install a newer .mcpb over the current one, or manage it in Settings, then Extensions. Remove and reinstall to reset.
• npx clients (Claude Code, Cursor, Windsurf, VS Code): npx -y jd-intel-mcp picks up new versions from npm's cache (within ~24h). Force it now with npx clear-npx-cache, then restart the client.
• Library or CLI: npm install jd-intel@latest (force latest) or npm update jd-intel (respect semver).

The company registry refreshes on its own: jd-intel fetches the current list at startup and falls back to the bundled copy offline, so new companies show up without reinstalling.

MCP tools

Plus one Resource: registry://jd-intel/all. Full company registry, grouped by ATS. Fetched lazily for broad catalog surveys.

What you get back

Every job normalizes to one schema, across every platform:

{  "id": "a1b2c3d4e5f6",  "company": "Example Co",  "title": "Senior Software Engineer, Platform",  "department": "Engineering",  "location": "Remote - US",  "locations": ["Remote - US", "Toronto, Canada"],  "locationType": "remote",  "workplace": { "type": "remote", "source": "ats" },  "salary": { "min": 180000, "max": 240000, "currency": "USD", "period": "year", "source": "text" },  "description": "Design and build the API surface our customers integrate against...",  "url": "https://boards.example.com/jobs/12345",  "postedAt": "2026-04-10T14:30:00Z"}

No custom parsing per company.

Data model

Platforms supported

Adding a new ATS is a single adapter file. See Contributing.

Filters (quick reference)

All filters AND together. Deep dive on patterns and gotchas: docs/filters.md.

Roadmap

Shipped

• Library, CLI, and MCP server (three surfaces of one toolkit)
• Greenhouse, Ashby, Lever, SmartRecruiters, Teamtailor, Recruitee, Personio, Workable, Workday adapters
• Title, topic, location, and date filters
• Salary extraction from JD text
• Verified company registry (1,100+ companies)

Next

• Anthropic MCP marketplace submission

Planned

• Temporal tracking (when roles open, close, reopen)
• Change detection
• Resume-aware fit scoring

Contributing

Full details in CONTRIBUTING.md. The short version:

Add companies to the registry: don't hand-edit registry/*.json. Stage your candidates in tmp/candidates.json, then run the live gate, which calls every board for real and keeps only the ones returning live jobs:

node scripts/verify-registry.mjs --candidates tmp/candidates.json --limit 50node scripts/append-registry.mjsnpm run sync:registry-pagesnode --test test/*.test.js

Entries that haven't passed the gate can't be merged. A board that looks right but returns nothing fails silently inside someone's search, which is worse than the company simply being absent. Workday needs a config of {tenant, env, site} read off the company's real careers URL, never constructed by pattern. CONTRIBUTING.md covers how to find and confirm those.

Add an ATS adapter: new file in src/adapters/. One adapter, one file. Follow the pattern of the existing adapters.

Request a company: open an issue. Tell me who's missing. That's a useful contribution on its own.

Built by

Prashant R. PM who builds. I try out and build what really matters below the AI hype.

• Portfolio and writing: prashantrana.xyz
• LinkedIn

License

MIT