
Connects Claude to Remotive's curated remote job listings via three focused tools: search jobs by keyword, category, or company; list all available categories with slugs; and pull full company profiles with active postings. Runs through Pipeworx's gateway infrastructure, which also offers an ask_pipeworx natural language interface if you'd rather skip direct tool calls. Useful when you're building job search workflows, need to filter remote positions programmatically, or want to track specific companies' hiring activity. The streamable HTTP transport means it works with any MCP client that supports remote servers. Part of a larger 673+ data source gateway, but available standalone if Remotive data is all you need.
Remotive MCP — curated remote-only job board. No auth.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
search(search?, category?, company_name?, limit?) — job listingslist_categories() — available categories (software-dev, design, marketing, ...)get_company(slug) — company profile + active listingshttps://remotive.com/api/remote-jobs — keyless, public REST.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"remotive": {
"url": "https://gateway.pipeworx.io/remotive/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/remotive/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_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.
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 Remotive data" })
The gateway picks the right tool and fills the arguments automatically.
MIT