---
title: "Search millions of jobs from your AI agent with the JobsPipe MCP server"
description: "Connect Claude, Cursor, or any MCP client to JobsPipe with your API key and search 30+ job sources from inside your agent. How it works, four use cases, and a one-line setup."
canonical: https://jobspipe.dev/blog/jobspipe-mcp-server
---

[NewSearch millions of jobs from your AI agent with MCP→](/blog/jobspipe-mcp-server)

[All posts](/blog)

![](/listly/card-field.png)

ProductServer

Product·Jun 24, 2026·5 min read

# Search millions of jobs from your AI agent with the JobsPipe MCP server

Connect Claude, Cursor, or any MCP client to JobsPipe with your API key and search 30+ job sources from inside your agent. How it works, four use cases, and a one-line setup.

![Dvir Atias](/authors/dvir-atias.jpg)

Dvir Atias

Founder, JobsPipe

JobsPipe now runs a [Model Context Protocol](https://modelcontextprotocol.io) server, so any MCP-capable client - Claude, Cursor, or your own agent - can search live job postings directly. No HTTP plumbing, no SDK, and no API key to paste: you point the client at one URL, sign in with your JobsPipe account when prompted, and the agent gets a `search_jobs` tool it can call on its own.

```
https://mcp.jobspipe.dev/mcp
```

## What you can build with it

The MCP server turns “every job posting, one API” into a capability your agent reaches for the same way it reaches for web search. A few things teams are doing with it:

-   **Job-search copilots.** Natural language in, structured postings out. “Find remote senior Rust roles posted this week” becomes a single tool call with the right filters.
-   **Sales and recruiting intelligence.** A new posting is a strong buying and outreach signal. Have an agent watch for companies hiring a specific role or stack and push that into your CRM or sequencing tool.
-   **Market and hiring-trend research.** Ask for totals with date and location filters to size demand - how many remote data-engineering roles opened in the US in the last 14 days.
-   **Dataset enrichment.** Feed a list of target companies and attach their live hiring activity to an existing account list.

## How it works

The server is a thin layer over the JobsPipe API. On first connect your client opens a browser window and you sign in with your JobsPipe account - no API key to copy, no header to configure. After that, results, sources, and freshness are identical to the REST API, usage counts against your plan, and your plan quota and rate limits apply.

## Connect in one line

With Claude Code:

```
claude mcp add --transport http jobspipe https://mcp.jobspipe.dev/mcp
```

For clients that read a JSON config (Cursor and similar), use the streamable-HTTP form:

```
{
  "mcpServers": {
    "jobspipe": {
      "url": "https://mcp.jobspipe.dev/mcp"
    }
  }
}
```

When the client prompts, sign in with your JobsPipe account (in Claude Code, run `/mcp` to authenticate). Once connected, the tools appear automatically.

## The search\_jobs tool

Every filter is optional and combined with AND - title and description phrases, company names, country codes, employment type, seniority, remote, a posted-after date or max age, plus paging. A typical call:

```
{
  "job_title_or": ["data engineer"],
  "remote": true,
  "posted_at_max_age_days": 14,
  "limit": 25,
  "include_total_results": true
}
```

The response mirrors the REST API: a `metadata` block with a total count and a paging cursor, and a `data` array of normalized postings - title, company, location, country, salary range, seniority, posting date, and the apply URL. The full filter set and response schema live in the [MCP docs](/docs/ai-agents/mcp).

Search 30+ job sources from your agent - free tier with 1,000 credits to start.

![](/listly/shape-heart.png)

FAQs

## Frequently Asked Questions

### How do I connect the JobsPipe MCP server to Claude or Cursor?

Point your MCP client at https://mcp.jobspipe.dev/mcp - no API key or header needed. With Claude Code it is one command: claude mcp add --transport http jobspipe https://mcp.jobspipe.dev/mcp, then sign in with your JobsPipe account when prompted. For clients that read a JSON config, such as Cursor, use the streamable-HTTP form with just the url field. Once connected, the tools appear automatically.

### What is a jobs MCP server?

A jobs MCP server lets any MCP-capable client search live job postings directly, with no HTTP plumbing and no SDK. The JobsPipe server gives your agent a search\_jobs tool it can call on its own. Every filter is optional and combined with AND: title and description phrases, company names, country codes, employment type, seniority, remote, a posted-after date or max age, plus paging. Responses mirror the REST API.

### Do I need a separate API key for the JobsPipe MCP server?

No, you authenticate with the same key you use for REST, one that starts with jp\_live\_, and the server forwards your calls under that key. Results, sources, and freshness are identical to the API, usage counts against your plan, and your plan quota and rate limits apply. There is no separate login, no OAuth dance, and no extra secret to manage. Grab a key from your dashboard.

[

← Previous

Job board API: the data layer for the job board you are building

](/blog/job-board-api-guide)[

Next →

Upwork statistics 2026: what 5,000 live job listings reveal

](/blog/upwork-statistics-2026)

---
Canonical URL: https://jobspipe.dev/blog/jobspipe-mcp-server
Title: Search millions of jobs from your AI agent with the JobsPipe MCP server
Description: Connect Claude, Cursor, or any MCP client to JobsPipe with your API key and search 30+ job sources from inside your agent. How it works, four use cases, and a one-line setup.

---
AI agents: the full machine-readable index of this site is https://jobspipe.dev/llms.txt?src=md-twin - API quickstart, no-key sandbox (POST https://api.jobspipe.dev/v1/sandbox/jobs/search), MCP server, pricing. Free key: https://jobspipe.dev/signup