Us MCP Server

Us MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server + standalone TypeScript SDK for 40+ U.S. government and international data APIs. 300+ tools with WASM-sandboxed code mode for context reduction. Covers Treasury, FRED, BLS, BEA, EIA, Census, FEC, Congress, Federal Register.

What you get

300+ tools covering economic, fiscal, health, education, energy, environment, lobbying, housing, patents, safety, banking, consumer protection, workplace safety, transportation, seismic, clinical trials, pharma payments, research funding, procurement, and legislative data.

• 300+ tools — across 40+ government APIs — economic, health, legislative, financial, environmental, and more
• Cross-referencing — — built-in instructions guide the LLM to combine data from multiple agencies (e.g., FDA adverse events + lobbying spend + campaign contributions)
• Code mode — — WASM-sandboxed JavaScript execution reduces context window usage by 98-100% for large responses
• Selective loading — — load only the modules you need: --modules fred,treasury,congress
• Dual transport — — stdio for desktop clients, HTTP Stream for web/remote
• TypeScript SDK — — every API is importable as a standalone typed client, no MCP required

Setting it up

The server ships on npm as us-gov-open-data-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

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

• Cross-referencing — built-in instructions guide the LLM to combine data from multiple agencies (e.g., FDA adverse events + lobbying spend + campaign contributions)
• Disk — backed caching** — responses cached to disk, survives restarts
• Category — APIs
• Economic — Treasury, FRED, BLS, BEA, EIA
• Legislative — Congress.gov, Federal Register, GovInfo, Regulations.gov
• Financial — FEC, Senate Lobbying, SEC, FDIC, CFPB
• Spending — USAspending, Open Payments
• Environment — EPA, NOAA, NREL, USGS
• Justice — FBI Crime Data, DOJ News
• Education — NAEP, College Scorecard, USPTO
• Demographics — Census, HUD, FEMA
• Other — BTS, USDA NASS, USDA FoodData, World Bank

Configuration and credentials

You will need 2 environment variables: FRED_API_KEY, DATA_GOV_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

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.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Us.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the us 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. Us's toolset — Cross-referencing, Disk, Category and 9 more — is a fair guide to whether it matches your workflow. It is maintained by lzinga; 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.