Give your AI client access to Hidden Jobs.

Connect any MCP-compatible client to search remote tech jobs, read descriptions, and open original application links when the account has the right subscription access.

Create an API key View on GitHub

Remote MCP URL

https://api.hiddenjobs.dev/mcp

HTTPRemote server

JSON-RPCStreamable HTTP

3Available tools

Start here

Connect your MCP client

Create an API key, add the remote URL to your MCP client, and send the key as a bearer token.

Remote server URL

https://api.hiddenjobs.dev/mcp

For clients that accept a JSON server configuration, use this starting point:

{
  "mcpServers": {
    "hidden-jobs": {
      "url": "https://api.hiddenjobs.dev/mcp",
      "headers": {
        "Authorization": "Bearer hj_live_..."
      }
    }
  }
}

Keep the API key private. Hidden Jobs shows the full key only once. Store it in your MCP client's secret or environment-variable configuration.

Security

One key, the same access rules

The MCP adapter forwards your bearer token to the Hidden Jobs REST API. It never uses a Supabase key in your client and it never bypasses subscription checks.

Create a Hidden Jobs API key

Choose the scopes and limits from the API keys dashboard. The MCP uses jobs:read for search and job details, and application-links:read for the gated application link tool.

Open API keys

Send the bearer token

Authorization: Bearer hj_live_...

Available tools

Three focused tools

The server exposes only job discovery and the subscription-gated application link. There is no auto-apply tool.

TOOL search_jobs jobs:read

Search the job board

Search by keywords, role, skills, company, category, employment type, job type, remote location, page, and limit.

queryKeywords, role, skills, or company.

categoryJob category.

employmentTypeEmployment type.

jobTypeJob type.

remoteLocationFor example Europe or Germany.

pagePage number, starting at 1.

limitBetween 1 and 50.

TOOL get_job jobs:read

Read one job

Load the public details and full description using the UUID or slug returned by search_jobs. The response does not contain the original application URL.

Required argument: idOrSlug

TOOL open_application_link Subscription

Open the original application link

Requires application-links:read and an active Hidden Jobs Access subscription for the API key owner. Without it, the tool returns a clear subscription-required error.

Required argument: idOrSlug

Important behaviour

What the MCP can return

Job information

The MCP can search offers and read their descriptions, companies, locations, skills, and other public metadata.

Requires jobs:read

Original application URL

The source URL is withheld from search and job-detail results. It is returned only by the dedicated tool after the subscription check succeeds.

Subscription + application-links:read

Under the hood

Streamable HTTP and JSON-RPC

The endpoint accepts MCP JSON-RPC requests over HTTP POST. Most MCP clients handle the protocol details for you.

Example tools/call messageJSON-RPC

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "search_jobs",
    "arguments": {
      "query": "typescript",
      "remoteLocation": "Europe",
      "limit": 10
    }
  }
}

initializeNegotiate protocol capabilities.

tools/listDiscover the available tools.

tools/callRun a job search or lookup.

Troubleshooting

Errors

Tool errors include a readable message and the underlying API status in structured content.

StatusMeaningWhat to do

401Missing, invalid, revoked, or expired API key.Configure the hj_live_... bearer token.

402Active subscription required for the application link.Activate Hidden Jobs Access for the key owner.

403The key does not have the required scope.Update the key scopes from the dashboard.

429Per-minute or monthly limit reached.Respect the limit or update the API key.

Need the raw API?

Use REST directly.

For server-to-server integrations, browse the complete endpoint reference and OpenAPI schema.

Read REST API docs