MCP recipe server

indeed mcp

Automate the Indeed employer dashboard from any MCP client. There is no official Indeed API — so each tool hands your client a browser-harness recipe it runs locally against your own signed-in Chrome.

tools
10
stateless transport
HTTP
paused by default
$0
get keys
01

Connect

Add it as an HTTP connector. The endpoint is gated by your API key — create one at /keys. Claude Desktop can't send headers, so the key rides in the URL path; for Claude Code use the x-api-key header.

endpointhttps://indeed.42nights.dev/api/mcp
claude desktop — connector url
https://indeed.42nights.dev/api/mcp/<YOUR_KEY>
claude code cli
claude mcp add --transport http \
  --header "x-api-key: $INDEED_MCP_KEY" \
  indeed-mcp https://indeed.42nights.dev/api/mcp
02

Tools

10 indeed_* tools. Each returns a Python recipe + payload schema; postings land pending (chargeable) — always follow with pause_job to reach the only safe state.

Postings

indeed_create_posting

Create a new posting on the on-file card, then pause it so it never charges.

indeed_reuse_posting

Clone an existing posting as a template into a fresh one.

Lifecycle

indeed_scan_jobs

List every posting with a stable id, title, location, and status — the foundation the others build on.

indeed_pause_job

Pause a posting — the only $0-safe state.

indeed_resume_job

Reactivate a paused posting.

indeed_close_job

Close a live posting for good.

indeed_delete_draft

Delete a draft posting.

Applicants

indeed_fetch_applicants

Pull the applicant list for a posting.

indeed_get_applicant_detail

Open a single applicant's full profile and resume.

indeed_send_candidate_message

Message candidates — stops before Send by default.

03

What you need

  • browser-harness on your $PATH (the client runs the recipe; the server never touches a browser).
  • Chrome signed into employers.indeed.com.
  • An MCP client with shell + file-write tools to run the recipe.