Add Jobby.dev to Claude Desktop in one config file. ~5 minutes including token mint.

1. Mint a token

Head to /account/api-tokens. Mint a token with whichever scopes you want Claude to have — recommended starter set: profile:read, queue:read, queue:write, matches:read. Save it somewhere safe; it's shown once.

2. Open the Claude Desktop config

In Claude Desktop: Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default editor.

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

3. Add the Jobby.dev server

{
  "mcpServers": {
    "jobbydev": {
      "command": "npx",
      "args": ["-y", "@jobbydev/mcp"],
      "env": {
        "JOBBYDEV_API_TOKEN": "jbb_..."
      }
    }
  }
}

If you already have other MCP servers in mcpServers, add the jobbydeventry as a sibling. Don't duplicate the outer mcpServers key.

4. Save and restart Claude Desktop

Save the file. Quit Claude Desktop completely (Cmd+Q on macOS, right-click tray icon → Quit on Windows) and reopen. The jobbydev_* tools should appear in the tools list.

5. Try it

In a new chat, ask:

Are there any live job-fair events on Jobby.dev right now?

Claude should call jobbydev_live_now and surface the results.

Troubleshooting

Tools don't appear. Check the Settings → Developer panel for an error indicator next tojobbydev. Most common cause: malformed JSON. Validate the file in jsonlint.
npx not found. Install Node.js 20+ from nodejs.org.
401 errors when tools fire. Token is wrong or revoked. Re-mint and update the env section.

See MCP troubleshooting for more.

Pinning a specific version

By default npx -y @jobbydev/mcpresolves to the latest published version on every Claude Desktop start. To pin a specific version (recommended for production agentic workflows so an upstream bump can't break your integration mid-conversation):

{
  "mcpServers": {
    "jobbydev": {
      "command": "npx",
      "args": ["-y", "@jobbydev/mcp@1.2.3"],
      "env": { "JOBBYDEV_API_TOKEN": "jbb_..." }
    }
  }
}

Multiple Jobby.dev accounts

You can run multiple Jobby.dev MCP servers side-by-side with different tokens (e.g. a personal seeker account + a recruiter team account, or one token per company you consult for):

{
  "mcpServers": {
    "jobbydev-personal": {
      "command": "npx",
      "args": ["-y", "@jobbydev/mcp"],
      "env": { "JOBBYDEV_API_TOKEN": "jbb_personal_..." }
    },
    "jobbydev-acme": {
      "command": "npx",
      "args": ["-y", "@jobbydev/mcp"],
      "env": { "JOBBYDEV_API_TOKEN": "jbb_acme_..." }
    }
  }
}

Tools then appear as jobbydev_personal_live_now and jobbydev_acme_live_now — Claude picks the right one based on conversational context (or you can ask explicitly).

Install: Claude Desktop