The Jobven MCP server lets your coding assistant search Jobven jobs and companies with your API key. Every result carries the REST request that produced it, as a URL and a curl command, so a search you try in chat goes straight into your code.

Connect your assistant

Each config reads the key from the JOBVEN_API_KEY environment variable or a prompt. A key written into the file itself ends up in your editor settings or in a .mcp.json you may commit.

export JOBVEN_API_KEY="your-api-key"

{
  "mcpServers": {
    "jobven": {
      "type": "http",
      "url": "https://api.jobven.com/mcp",
      "headers": {
        "X-API-Key": "${JOBVEN_API_KEY}"
      }
    }
  }
}

{
  "mcpServers": {
    "jobven": {
      "url": "https://api.jobven.com/mcp",
      "headers": {
        "X-API-Key": "${env:JOBVEN_API_KEY}"
      }
    }
  }
}

{
  "inputs": [
    {
      "type": "promptString",
      "id": "jobven-api-key",
      "description": "Jobven API key",
      "password": true
    }
  ],
  "servers": {
    "jobven": {
      "type": "http",
      "url": "https://api.jobven.com/mcp",
      "headers": {
        "X-API-Key": "${input:jobven-api-key}"
      }
    }
  }
}

[mcp_servers.jobven]
url = "https://api.jobven.com/mcp"
env_http_headers = { "X-API-Key" = "JOBVEN_API_KEY" }

Then ask your assistant something like "find remote TypeScript jobs posted this week and show me the request".

Tools

Every tool is read-only. None of them create, change or delete anything on your account.

The request behind each result

search_jobs, get_job, search_companies and get_company each return a request with the exact call they made:

{
  "method": "GET",
  "url": "https://api.jobven.com/v1/public/jobs?q=engineer&remoteType=remote&limit=10&descriptionFormat=plain",
  "curl": "curl -H \"x-api-key: $JOBVEN_API_KEY\" 'https://api.jobven.com/v1/public/jobs?q=engineer&remoteType=remote&limit=10&descriptionFormat=plain'"
}

The curl command reads your key from $JOBVEN_API_KEY. Your key never appears in a tool result.

search_jobs asks for plain-text descriptions and returns an excerpt of each, so a page of jobs stays small in your assistant's context. In your own code, drop descriptionFormat=plain for HTML, or use markdown or all, and raise limit to your plan's page size (25 on Free, 50 on Starter, 100 on Growth and above).

Testing a webhook receiver

webhook_example returns a delivery exactly as your endpoint receives one: the raw body, every header, and a Jobven-Signature signed with an example secret. The verifier it returns is the one in Signature verification, and it accepts the sample for 300 seconds, so you can POST the sample to your receiver and check it end to end. Real deliveries are signed with your subscription's own signing secret, shown once when you create the subscription in the dashboard.

Usage and limits

MCP calls go through the same API as your code: the same key checks, burst limit, monthly allowance and usage counts on your dashboard.

When a call is refused, the tool returns the API's own message so your assistant can explain it:

Listing the tools and webhook_example need no key, so you can try the server, and directories and inspectors can see what it offers, before you sign up.