Connect JobsPipe to your assistant

JobsPipe is one MCP server, reachable from any assistant that supports remote MCP:

https://mcp.jobspipe.dev/mcp

Some assistants list JobsPipe in their directory, so connecting is one click. The rest let you add it as a custom connector by pasting that URL. Either way the assistant sends you through a JobsPipe sign-in the first time, and a free account is enough to start. There is no key to copy for any of the assistants on this page; the MCP server page covers keys for scripts and config-file clients.

Once connected, ask in plain language — "remote senior data engineers hiring in Germany this week", "is Stripe hiring for sales right now?" — and the assistant calls the tools itself.

Claude

From the directory (web, desktop, mobile): open Settings → Connectors, search for JobsPipe and click Connect. Sign in when Claude asks.

As a custom connector:

1. Settings → Connectors → Add custom connector.
2. Paste https://mcp.jobspipe.dev/mcp as the remote MCP server URL. Leave Advanced settings empty.
3. Click Connect and sign in to JobsPipe.

On Team and Enterprise plans an owner adds the connector once under Organization settings → Connectors; each member then connects their own JobsPipe account from Settings → Connectors.

Claude Code: claude mcp add --transport http jobspipe https://mcp.jobspipe.dev/mcp, then /mcp → Authenticate. Details and the API-key variant are on the MCP server page.

ChatGPT

ChatGPT connects to JobsPipe as a plugin backed by the MCP server. It needs Developer mode once.

1. Open Settings → Security and login and turn on Developer mode.
2. Open Settings → Plugins, click +, name it JobsPipe, enter https://mcp.jobspipe.dev/mcp as the MCP server URL and leave Authentication on OAuth.
3. Click Create, then Connect, and sign in to JobsPipe.

If Browse plugins shows a JobsPipe entry that displays curl commands and asks for an API key, that is an older skill document rather than this server; remove it and create the plugin above. ChatGPT's deep research can also use JobsPipe as a source, since the server answers the search and fetch tools it looks for.

Gemini

The Gemini app takes custom MCP apps under Connected Apps. Google currently limits custom apps to personal Google accounts, users 18+ in the US, English, with Keep Activity on; adding is web-only but the app then works on mobile too.

1. On a computer, open gemini.google.com, click Settings (bottom left) → Connected Apps. If it is missing, open Personal Intelligence first.
2. Under Custom apps, click Add a custom app and paste https://mcp.jobspipe.dev/mcp. Leave Advanced features alone — JobsPipe registers the client itself, so no credentials are needed.
3. Click Next and sign in to JobsPipe.

Gemini CLI: gemini extensions install https://github.com/jobspipe/mcp installs JobsPipe as an extension; sign in on first use.

Grok

Custom MCP connectors are available on paid Grok accounts.

1. Web: click + in the composer → Connectors → + Add connector. Mobile: Settings → Connectors.
2. Choose a custom MCP connector, name it JobsPipe and enter https://mcp.jobspipe.dev/mcp.
3. Complete the sign-in Grok opens.

Perplexity

Custom connectors are available on Pro, Max and Enterprise.

1. Click your profile (bottom left) → All settings → Connectors.
2. Click + Custom connector. Name it JobsPipe, set the MCP server URL to https://mcp.jobspipe.dev/mcp and the transport to Streamable HTTP.
3. Under Advanced, set Authentication to OAuth and leave the client ID and secret empty — Perplexity discovers JobsPipe's authorization server and registers itself.
4. Tick the acknowledgement and click Add, then sign in when prompted.

Mistral Le Chat

Le Chat adds custom MCP connectors at the workspace level, so this needs an administrator; every member then connects their own account.

1. In the navigation menu open Intelligence → Connectors and click + Add Connector.
2. Switch to the Custom MCP Connector tab. Connector name jobspipe (no spaces), server URL https://mcp.jobspipe.dev/mcp, an optional description.
3. Click Connect. Le Chat detects the sign-in method and walks each user through it the first time they use the connector.

Cursor

From the marketplace: type /add-plugin jobspipe in chat, or open Settings → Plugins, search JobsPipe and click Install. Sign in when prompted.

By hand: add {"mcpServers":{"jobspipe":{"url":"https://mcp.jobspipe.dev/mcp"}}} to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project), then sign in from Settings → MCP. The MCP server page has the one-click install badge and the API-key form.

VS Code, Windsurf and other MCP clients

Config-file clients are covered on the MCP server page: VS Code and GitHub Copilot (.vscode/mcp.json, one-click badges), Windsurf, and the generic shape for anything else. Clients that implement MCP authorization need only the URL; the rest send an API key as a header.

Checking it worked

Every assistant lists nine JobsPipe tools once connected. Ask it "which JobsPipe plan am I on?" — that runs get_account_info, costs nothing, and confirms the connection landed on the right account. If the assistant says it has no usable key or never shows a sign-in screen, it is talking to something other than https://mcp.jobspipe.dev/mcp; re-add the connector with that exact URL.

Searches draw on your plan's monthly credits; saving a search as a signal instead of re-running it costs none. See Limits and errors for what an exhausted quota looks like inside an assistant.