@hirejack/mcp

Model Context Protocol server that exposes HireJack's tech job market intelligence to MCP-compatible clients (Claude Desktop, Claude Code, Cursor, Cline, etc.) — tech jobs, companies, skills, salaries, hiring trends.

Quick start

Claude Code:

claude mcp add hirejack -- npx -y @hirejack/mcp

Claude Desktop — edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "hirejack": {
      "command": "npx",
      "args": ["-y", "@hirejack/mcp"]
    }
  }
}

Restart Claude Desktop. Then try:

• "Find remote senior backend roles paying $200K+ that sponsor visas"
• "What is Stripe currently hiring?"
• "Which fintech companies are scaling fastest?"
• "What skills are trending in tech right now?"

The npm package uses stdio transport — no auth, runs locally as a subprocess. The public tools work out of the box. Pro+ intelligence tools (match_job, company_fit, resume_rewrite, etc.) require an authenticated user; for that you'll want the hosted HTTP transport at https://hirejack.com/api/mcp once the claude.ai connector regression is resolved (see below).

Why stdio first? The hosted HTTP transport at https://hirejack.com/api/mcp works end-to-end via direct API (curl/SDK), but claude.ai's web connector and Claude Desktop's remote MCP UI have an upstream auth-handshake regression that drops the connection after OAuth succeeds. Stdio sidesteps the bug entirely. Tracking: anthropics/claude-ai-mcp#136.

Transports

Tools

Public (no auth required):

Pro tier (requires authenticated HireJack user with pro or higher):

Premium tier (requires premium):

Analyst (Pro+ tier today; will tighten to a dedicated analyst tier when that pricing plan ships):

Pro+ tools are thin wrappers over the website's existing intelligence Lambdas. Tier gating happens server-side in those Lambdas — the MCP server just forwards the user's identity. If the user lacks the required tier, the API returns 403 and the tool surfaces a clear upgrade hint.

Build from source

git clone https://github.com/TVLSS/hirejack-mcp
cd hirejack-mcp
npm install
npm run build       # tsc → dist/
node dist/index.js  # waits on stdin/stdout for JSON-RPC

Releasing

Publishing is automated by GitHub Actions (.github/workflows/release.yml). Pushing a version tag builds, publishes to npm, and updates the MCP Registry:

npm version patch          # bumps package.json + creates the vX.Y.Z tag
git push && git push --tags

The workflow verifies the tag matches package.json, then runs npm publish (using the NPM_TOKEN repo secret) and a best-effort MCP Registry update via GitHub OIDC. Keep server.json's version in step with package.json.

Configuration

The npm package ships the stdio transport only. The hosted HTTP+OAuth endpoint at https://hirejack.com/api/mcp is run separately by HireJack and not implemented in this repo.

Project layout

src/
├── index.ts            # stdio entry point
├── registry.ts         # transport-agnostic tool registry
├── lib/
│   ├── api.ts          # HireJack REST client
│   ├── format.ts       # tool result helpers
│   └── proAuth.ts      # Pro+ auth check (returns "use hosted endpoint" in stdio)
└── tools/              # 22 tool implementations

License

MIT — see LICENSE.

Support

• Issues / feature requests: https://github.com/TVLSS/hirejack-mcp/issues
• General feedback: https://hirejack.com/feedback.html
• Site / product: https://hirejack.com