Skip to main content
Glama
pipeworx-io

mcp-remoteok

by pipeworx-io

mcp-remoteok

RemoteOK MCP — remote-work job board (tech-heavy), keyless.

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Tool

Description

list_jobs

List the most recent remote jobs from RemoteOK (a popular, tech-heavy remote-work job board; keyless). Returns the newest postings (id, position, company, location, tags, salary range, date, url) without the long HTML description. Salaries are USD when present (0 = not disclosed).

search_jobs

Keyword-search current RemoteOK remote-job listings. Matches the query (case-insensitive) against job position, company name, or any tag. Tech-heavy board; keyless. Returns matching postings (id, position, company, location, tags, salary range, date, url). Salaries are USD when present.

get_job

Get the full RemoteOK job posting for a given job id, including the full HTML description. Use an id returned by list_jobs or search_jobs. Only jobs in the current ~100 most-recent listings are available. Salaries are USD when present.

Related MCP server: remoote-mcp

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "remoteok": {
      "url": "https://gateway.pipeworx.io/remoteok/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/remoteok/mcp returns the tools in the table above plus the shared Pipeworx meta-toolsask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Remoteok data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables searching remote jobs by free-text, category, and company, listing job categories, and retrieving company profiles from the Remotive job board.
    4 npm
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to search and explore remote job listings, salary stats, and popular roles, and supports token-authenticated actions like job alerts and apply redirects.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables natural-language job search and aggregation from multiple recruitment websites with zero configuration, providing filtered results and standardized output for AI assistants.
    26 npm
    ISC