Remote Jobs Center MCP Server

A hosted Model Context Protocol server for searching current remote / work-from-home jobs — by category, region, perk, or company. Built so any MCP-enabled assistant or agent can query the Remote Jobs Center corpus directly and return ready-to-apply links.

Unlike single-board servers, the corpus is aggregated and deduped from multiple vetted remote job boards and employer career sites, then enriched with perks, skills, seniority, and AI-role flags — so a single query spans the whole remote market, not one source.

• Endpoint: https://remotejobscenter.com/mcp

• Transport: Streamable HTTP (JSON-RPC 2.0 over POST) — stateless, no auth

• Registry: com.remotejobscenter/remote-jobs (official MCP registry)

Connect

Claude (web/desktop): Settings → Connectors → Add custom connector → URL https://remotejobscenter.com/mcp. No authentication required.

Any MCP client that supports Streamable HTTP: point it at the endpoint above.

Related MCP server: remoet

Tools

Filter values

• category: software, data, design, marketing, sales, support, writing, product, finance, hr

• region: us, uk, europe, canada, latam, apac, worldwide

• perk: tuition-reimbursement, six-figure, no-degree, entry-level, four-day-week, visa-sponsorship, async, equity, unlimited-pto

• limit: default 20, max 50

Job shape

{
  "slug": "acme-senior-backend-engineer",
  "title": "Senior Backend Engineer",
  "company": "Acme",
  "category": "software",
  "region": "us",
  "location": "United States (Remote)",
  "salaryMin": 140000,
  "salaryMax": 180000,
  "perks": ["six-figure", "equity"],
  "source": "Employer careers",
  "postedAt": "2026-06-10T00:00:00.000Z",
  "applyUrl": "https://...",
  "url": "https://remotejobscenter.com/jobs/acme-senior-backend-engineer/"
}

get_job additionally includes a short excerpt.

Request / response examples

All requests are JSON-RPC 2.0 over POST https://remotejobscenter.com/mcp.

Initialize

curl -s https://remotejobscenter.com/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05"}}'

List tools

curl -s https://remotejobscenter.com/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

Search

curl -s https://remotejobscenter.com/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"search_remote_jobs","arguments":{"query":"python","region":"us","limit":5}}}'

A tools/call result wraps the tool's JSON output in a text content block:

{ "jsonrpc": "2.0", "id": 3, "result": {
    "content": [ { "type": "text", "text": "{\"total\":42,\"returned\":5,\"jobs\":[...]}" } ]
} }

Run locally (stdio)

The hosted endpoint above is the canonical deployment. For local use or registry introspection, this repo also ships a standalone stdio MCP server with the same tools and data source.

npm install
npm start            # runs src/server.mjs over stdio

Point any stdio MCP client at node /path/to/remotejobscenter-mcp/src/server.mjs.

Docker

docker build -t remotejobscenter-mcp .
docker run -i --rm remotejobscenter-mcp

The container speaks MCP over stdio, so registries (e.g. Glama) and MCP clients can start it and introspect its tools directly.

Implementation

Two equivalent surfaces, one data source:

• Hosted — a single Cloudflare Pages Function deployed at /mcp, speaking Streamable HTTP (JSON-RPC 2.0 over POST). Stateless, read-only, no auth. A GET with Accept: text/event-stream returns 405 (per the Streamable HTTP spec, since the server does not stream); a plain GET returns a small info document.

• Local / containerized — src/server.mjs, a stdio MCP server using the official @modelcontextprotocol/sdk.

Both read the same public corpus the website publishes at https://remotejobscenter.com/api/jobs.json (cached ~10 minutes), so there is one source of truth.

License

MIT — see LICENSE.