@pipeworx/us-econ-calendar

Connect: https://gateway.pipeworx.io/us-econ-calendar/mcp · Install: one-click buttons

Tools: 3

US macro-economic release SCHEDULE — when CPI, PPI, the Employment Situation (jobs report), JOLTS, FOMC meetings, weekly DOL jobless-claims reports and Treasury auctions happen, in Eastern Time. This pack answers when, never what the number was — for the released values, use bls or fred.

Tools

  • econ_calendar_upcoming({hours?, days?, types?}) — every tracked release falling in the next N hours/days, sorted by datetime.
  • econ_calendar_next({release, from?}) — the next occurrence of one release type (cpi, ppi, employment_situation, jolts, fomc, claims, treasury_auction).
  • econ_calendar_recent({days?}) — releases in the last N days (“what came out this week”).

Auth

Keyless. No platform key, no BYO key.

Data sources

Important gotcha: bls.gov cannot be fetched live

www.bls.gov’s entire host sits behind Akamai bot-management that rejects every automated client we tried on 2026-09-13 — bare curl, curl with a full browser header set (UA, sec-ch-ua-*, all four Sec-Fetch-*), and a live deployed Cloudflare Worker fetch() all got an immediate 403 Access Denied from AkamaiGHost, including on /robots.txt. This is not the “send a browser UA” class of block documented for war.gov/dol.gov/gao.gov — those pass with the right headers; bls.gov does not, from any of curl, a CF Worker, or (separately) data.bls.gov’s own general pages (its /timeseries/<series> data-table path is, oddly, NOT blocked — but it carries no schedule information, just series data). Because of this, the CPI/PPI/Employment-Situation/JOLTS tables in src/index.ts are a static, checked-in copy of what bls.gov’s schedule pages showed as of 2026-09-13, read via a real browser-backed fetch rather than scraped by this pack at runtime.

Refreshing it: re-read https://www.bls.gov/schedule/news_release/{cpi,ppi,empsit,jolts}.htm (a tool with real browser rendering — not curl, not a Workers fetch() — is required to get past the Akamai wall) and extend each *_SCHEDULE array. BLS publishes about a year ahead, so refresh before the tables run out — econ_calendar_next/_upcoming degrade honestly (schedule_not_yet_published) rather than guessing once a query runs past the last row, but that’s a worse answer than a refreshed table.

Treasury and the Fed calendar have no such problem — both are fetched live (Treasury directly; FOMC via fed-comms) and need no manual refresh.

Tools

  • econ_calendar_upcoming — Upcoming US macro release SCHEDULE — which of CPI, PPI, the Employment Situation (jobs report), JOLTS, an FOMC meeting/rate decision, the weekly DOL jobless-claims report, and Treasury auctions fall i
  • econ_calendar_next — When the NEXT occurrence of a specific US macro release is — next CPI, next PPI, next jobs report, next JOLTS, next FOMC meeting, next weekly jobless-claims report, or next Treasury auction — with its
  • econ_calendar_recent — What US macro releases happened in the last N days — ‘what was released this week’, ‘has CPI come out yet this month’. Lists CPI/PPI/Employment Situation/JOLTS/FOMC/claims/Treasury-auction events whos

Tools

  • econ_calendar_next — When the NEXT occurrence of a specific US macro release is — next CPI, next PPI, next jobs report, next JOLTS, next FOMC meeting, next weekly jobless-claims report, or next Treasury auction — with its
  • econ_calendar_recent — What US macro releases happened in the last N days — 'what was released this week', 'has CPI come out yet this month'. Lists CPI/PPI/Employment Situation/JOLTS/FOMC/claims/Treasury-auction events whos
  • econ_calendar_upcoming — Upcoming US macro release SCHEDULE — which of CPI, PPI, the Employment Situation (jobs report), JOLTS, an FOMC meeting/rate decision, the weekly DOL jobless-claims report, and Treasury auctions fall i

Regenerated from source · build September 13, 2026