Federal Register MCP Server

Federal Register MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Federal Register proposed/final rules, notices, executive orders, FAR cases. 8 tools.

What you get

Eight free and open source MCP servers for federal contracting data and policy tracking, packaged as Claude Desktop Extensions (.mcpb) for one-click install.

• Deterministic. — MCP servers execute tested Python. Claude does not generate API-call code on the fly. Same input, same output
• One-click install. — .mcpb bundles prompt for API keys at install time and register tools automatically. Contracting officers install them the same way they install any app
• Low context cost. — Tool schemas are ~100 tokens each. The deprecated API-data skills cost 500-1000 lines of context per run
• Production-hardened. — Each MCP went through 3-6 audit rounds with live testing against its production API
• Cross-client. — MCP is an open standard. Same servers run in Claude Desktop, Claude Code, Cursor, Cline, Zed, Continue

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once Federal Register is connected, these are the calls the assistant has available:

• One — click install.** .mcpb bundles prompt for API keys at install time and register tools automatically. Contracting officers install them the same way
• Production — hardened.** Each MCP went through 3-6 audit rounds with live testing against its production API
• Cross — client.** MCP is an open standard. Same servers run in Claude Desktop, Claude Code, Cursor, Cline, Zed, Continue

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the federal register mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Federal Register's toolset — One, Production, Cross — is a fair guide to whether it matches your workflow. It is maintained by 1102tools; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.