
Connects Claude to the Bureau of Labor Statistics public data API v2, giving you programmatic access to employment figures, inflation metrics, wage data, and other economic statistics. Part of the Pipeworx gateway ecosystem, which means you can either use it standalone or access it alongside 673+ other data sources through a unified endpoint. The ask_pipeworx tool lets you query BLS data in plain English rather than crafting specific API calls. Useful when you're analyzing economic trends, building reports that need official labor statistics, or answering questions that require current unemployment rates, CPI numbers, or occupational employment data.
The U.S. Bureau of Labor Statistics's data warehouse. Employment, unemployment, wages, prices (CPI/PPI), productivity, occupational projections — the official US labor and price data. National, state, and metro level. Free with a registered API key.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Anything labor-market or inflation-related at the official level: BLS. Where FRED gives you headline series, BLS gives you the underlying detail (occupation-level, industry-level, MSA-level). Agents researching local economic conditions, sector wages, or specific CPI components reach BLS directly.
Three core flows:
1. Look up a series. "What's the metro Denver unemployment rate?" → bls_search({query: "Denver unemployment"}) → series IDs. Then bls_get_series({series_id}) for values.
2. Latest value. "What's national unemployment right now?" → bls_latest({series_id: "LNS14000000"}) → most recent observation.
3. Browse popular series. "What does BLS publish?" → bls_popular_series → curated list of high-traffic IDs.
BLS API requires a free key from https://www.bls.gov/developers/. Without it, calls are throttled to ~25/day per IP. With a key, it's 500/day. Pass via _apiKey per call.
BLS series IDs encode survey, area, sector, and data type. Examples:
| Series ID | What it is |
|---|---|
LNS14000000 | National unemployment rate (seasonally adjusted) |
CES0000000001 | Total nonfarm employment (national) |
CUUR0000SA0 | CPI all items, US city average, not seasonally adjusted |
LAUMT080000000000003 | Denver MSA unemployment rate |
WPSFD49207 | PPI for finished goods |
Don't try to construct IDs from scratch — use bls_search or bls_popular_series.
| Data | Release timing |
|---|---|
| Employment situation (national + state) | First Friday of the month |
| CPI | Mid-month (around the 10th-15th) |
| PPI | Mid-month, day after CPI |
| Metro unemployment (LAUS) | ~3 weeks after the reference month |
| Productivity | Quarterly, ~5 weeks after quarter end |
Pipeworx caches BLS responses with TTLs aligned to release schedules.
LNS = SA, LNU = NSA). Mixing them is the most common analyst error.CPIAUCSL with the pc1 units transformation (which does it for you).Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"bls": {
"url": "https://gateway.pipeworx.io/bls/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/bls/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 Bls data" })
The gateway picks the right tool and fills the arguments automatically.
MIT