The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Onet listing page.
ONET MCP — wraps the ONET Web Services (US DOL) occupation taxonomy
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
| Tool | Description |
|---|---|
onet_search | Search occupations by keyword. Returns matching O*NET occupations with SOC code, title, and relevance score. Example: onet_search({ keyword: "data scientist", _apiKey: "username:password" }) |
onet_occupation | Occupation detail for an O*NET-SOC code. Returns title, description, alternate names, and sample reported job titles. Example: onet_occupation({ code: "15-1252.00", _apiKey: "username:password" }) |
onet_skills | Skills for an occupation. Returns the ranked skill elements (name, description, importance score) for an O*NET-SOC code. Example: onet_skills({ code: "15-1252.00", _apiKey: "username:password" }) |
onet_technology | Tools & technology used in an occupation. Returns technology categories and example software/tools for an O*NET-SOC code. Example: onet_technology({ code: "15-1252.00", _apiKey: "username:password" }) |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
tools/list at https://gateway.pipeworx.io/onet/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:
Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/onet_search. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
Or run it directly to confirm it starts:
It 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.
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:
The gateway picks the right tool and fills the arguments automatically.
MIT