NLRB MCP β US National Labor Relations Board case search: unfair labor
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
One-click editor setup isnβt available for this listing yet β we donβt have a confirmed install command, and weβd rather show nothing than point your editor at the wrong package or host. Follow the projectβs own setup instructions, linked above.
US National Labor Relations Board case search β unfair labor practice charges and union representation/election petitions (~516,000 cases), read live from the NLRB's public case search on nlrb.gov.
Part of Pipeworx β an MCP gateway connecting AI agents to 1683+ live data sources.
nlrb_search(query, case_type?, status?, filed_since?, filed_before?, region?, sort?, limit?, page?) β
finds cases by employer name, union name, or case number. Returns case
number, case name, date filed, open/closed status, city and NLRB region, plus
the total number of matching cases. Answers "is Starbucks facing an NLRB
charge", "union election petitions at Trader Joe's".nlrb_case(case_number) β the full docket for one case: allegations charged
under the National Labor Relations Act, status, location, region,
participants (charged party, charging party, employer, union, and their legal
representatives), the docket activity log, and β for representation cases
that reached a count β the election tally (eligible voters, ballots counted,
votes for and against the union).nlrb_recent_filings(days?, case_type?, status?, region?, limit?) β newest
filings nationally over a recent window, newest first, with the total filed in
that window.Keyless. No account, no registration, no key.
data
fields carry the rendered result HTML and whose trailing invoke command
carries the total match count in args[4].cases, plural. /get-search-data/{term}/case
is refused by the site's WAF with an HTTP 200 carrying a "Request
Rejected" HTML page β a rejection that reads as a success unless you inspect
the body. The pack checks for that page and returns
{ found: false, reason: 'blocked' }./ in it silently changes which
endpoint you hit. Slashes are stripped and the term is URL-encoded./search/case are ignored. The visible search form
POSTs; ?search_term=Starbucks returns the unfiltered 516k listing with the
header still reading "for all". Only /get-search-data/... honours a term.f[0]=case_type:C (or case_type:R, or
(case_type:C OR case_type:R)), s[n]=Open|Closed|Open - Blocked,
r[n]=<region>, state[n]=<XX>, and date_start/date_end in MM/DD/YYYY
β ISO dates are ignored rather than rejected, so the pack converts.desc (newest), asc (oldest) and relevance; rows and a
zero-based page both work, confirmed to rows=50.10-CB-393760): 2-digit region, case
type (CA/CB against an employer/union, RC/RD/RM for representation), serial.
The pack uppercases and zero-pads a single-digit region.Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
tools/list at https://gateway.pipeworx.io/nlrb/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.
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/nlrb_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
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/nlrb)<a href="https://allmcps.com/mcp/nlrb"><img src="https://allmcps.com/api/badge/nlrb?style=directory" alt="Nlrb on AllMCPs" /></a>