us-govdata-mcp

MCP server for US government data — search building permits, federal contract opportunities (SAM.gov), and the national healthcare provider registry (NPI/NPPES) from Claude, Cursor, or any Model Context Protocol client.

All three data sources are official government publications (city open-data portals, SAM.gov's public extract, the CMS NPPES API) — no HTML scraping, no logins, no fragile selectors. The heavy lifting is done by three production Apify actors that run on your own Apify account.

Try it in 30 seconds — no account, no charge

Before you decide whether this is worth an API token, run it with none:

{
  "mcpServers": {
    "us-govdata": {
      "command": "npx",
      "args": ["-y", "github:CBLU2005/us-govdata-mcp"],
      "env": { "APIFY_DRY_RUN": "1" }
    }
  }
}

That is the whole setup. In dry-run mode every tool returns realistic sample records plus the exact Apify API request it would have sent — so you can see the real shape of the data, confirm your agent calls the tools correctly, and read the pricing disclosure in each tool description, without creating an account, pasting a token, or spending anything.

Ask your agent something like "find building permits over $500k issued in Austin this month" and watch the tool call happen end to end. When you want live data, delete the APIFY_DRY_RUN line and add an APIFY_TOKEN (below).

Related MCP server: PubRecords MCP

Tools

* Honest pricing disclosure: these tools run paid, pay-per-result Apify actors published by CBLU. Your Apify account is charged only for records actually returned — there are no subscriptions or start fees. Every tool defaults to 25 results per call, so a typical call costs a fraction of a cent (25 permits ≈ $0.13; 25 contract notices ≈ $0.10; 25 providers ≈ $0.05). Apify's free plan includes monthly platform credit, which is enough to use these tools casually at no cost. Actor pages with full pricing details:

• US Building Permits Scraper

• SAM.gov Contract Opportunities Scraper

• NPI Registry Scraper

Quick start

1. Get an Apify token (free, ~2 minutes)

1. Sign up at https://console.apify.com/sign-up (free plan works).

2. Copy your API token from https://console.apify.com/settings/integrations.

The server starts and lists its tools without a token — the token is only needed when a tool is actually called.

2. Add the server to your MCP client

Claude Desktop (claude_desktop_config.json → Settings → Developer → Edit Config):

{
  "mcpServers": {
    "us-govdata": {
      "command": "npx",
      "args": ["-y", "github:CBLU2005/us-govdata-mcp"],
      "env": {
        "APIFY_TOKEN": "your_apify_token_here"
      }
    }
  }
}

Claude Code:

claude mcp add us-govdata -e APIFY_TOKEN=your_apify_token_here -- npx -y github:CBLU2005/us-govdata-mcp

Cursor / Windsurf / other MCP clients (same shape as Claude Desktop):

{
  "mcpServers": {
    "us-govdata": {
      "command": "npx",
      "args": ["-y", "github:CBLU2005/us-govdata-mcp"],
      "env": { "APIFY_TOKEN": "your_apify_token_here" }
    }
  }
}

From a local clone:

git clone https://github.com/CBLU2005/us-govdata-mcp.git
cd us-govdata-mcp
npm install && npm run build
# then point your client at: node /path/to/us-govdata-mcp/dist/index.js

Docker:

docker build -t us-govdata-mcp .
docker run -i --rm -e APIFY_TOKEN=your_apify_token_here us-govdata-mcp        # stdio
docker run --rm -p 3000:3000 -e APIFY_TOKEN=... us-govdata-mcp --http 3000    # Streamable HTTP

3. Ask your AI agent things like

• "Find building permits for new construction over $500k issued in Austin this month, with contractor names."

• "Any active small-business set-aside cybersecurity solicitations with a response deadline after today? Include the contracting officer's email."

• "List dentists in the greater Miami area (ZIP 331) with their practice phone numbers."*

Transports

• stdio (default) — what desktop MCP clients use: us-govdata-mcp

• Streamable HTTP — stateless endpoint at POST /mcp, health check at GET /healthz: us-govdata-mcp --http 3000 (or set MCP_HTTP_PORT=3000)

Environment variables

How it works

Each tool validates its arguments (zod), builds the actor input, and calls the Apify API's run-sync-get-dataset-items endpoint with your token via an Authorization: Bearer header (never in the URL). The actor runs on the Apify platform under your account and the resulting dataset items are returned directly as the tool result. This server keeps no state and sees no data beyond passing it through.

Development

npm install
npm test          # builds + runs the full smoke suite (introspection, tokenless
                  # error path, dry-run request construction, HTTP transport)

The test suite needs no Apify account and no network — it uses APIFY_DRY_RUN=1.

Related

• Apify Store profile with all CBLU actors: https://apify.com/cblu

• Model Context Protocol: https://modelcontextprotocol.io

License

MIT © CBLU