Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http arbeitnow 'https://gateway.pipeworx.io/arbeitnow/mcp'{
"mcpServers": {
"arbeitnow": {
"type": "http",
"url": "https://gateway.pipeworx.io/arbeitnow/mcp"
}
}
}@pipeworx/mcp-arbeitnowclaude mcp add arbeitnow -e 'PIPEWORX_API_KEY=<your pipeworx_api_key>' -- npx -y @pipeworx/mcp-arbeitnow@0.2.1{
"mcpServers": {
"arbeitnow": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-arbeitnow@0.2.1"
],
"env": {
"PIPEWORX_API_KEY": "<your pipeworx_api_key>"
}
}
}
}Environment variables
PIPEWORX_API_KEYsecret Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
mcp-arbeitnow
Arbeitnow Job Board MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1872+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
| Tool | Description |
|---|---|
list_jobs | List recent job postings from Arbeitnow, a keyless European (Germany-heavy) job board with many English-speaking and visa-sponsorship roles. Returns one page of postings in reverse-chronological order (newest first). HTML descriptions are omitted from this list — use get_job for the full description. Use page to paginate and remote_only to keep only remote jobs. |
search_jobs | Keyword-search recent Arbeitnow job postings (keyless European/German job board, many English-speaking & visa-sponsor roles). The upstream API has no search param, so this scans the most recent pages and filters client-side: it keeps jobs whose title, company name, or any tag contains the query (case-insensitive). Scans up to pages pages (default 3, max 10). Older jobs that have scrolled off the recent pages will not be found. |
get_job | Fetch the full details of a single Arbeitnow job posting by its slug, INCLUDING the full HTML description. There is no single-job endpoint upstream, so this scans the most recent pages (~3) to find the matching slug. If the job has scrolled off the recent listings it cannot be retrieved — use search_jobs instead. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"arbeitnow": {
"url": "https://gateway.pipeworx.io/arbeitnow/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/arbeitnow/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 1872+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/arbeitnow_list_jobs \
-H 'Content-Type: application/json' \
-d '{"page":1,"remote_only":false}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/arbeitnow_list_jobs. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"arbeitnow": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-arbeitnow"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-arbeitnowIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
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 Arbeitnow data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Frequently asked questions
What is Arbeitnow?
Arbeitnow Job Board MCP.
How do I install Arbeitnow?
It runs as a remote server. In Claude Code: claude mcp add --transport http arbeitnow 'https://gateway.pipeworx.io/arbeitnow/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Arbeitnow need an API key?
Yes. It expects PIPEWORX_API_KEY, which you set in its configuration.
Is Arbeitnow open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Arbeitnow?
It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.