SAM.gov MCP

What is SAM.gov MCP?

A Model Context Protocol server that wraps the SAM.gov REST APIs as deterministic tool calls. Built for federal contracting officers, GS-1102 contract specialists, and small business government contractors who need plain-English access to SAM.gov entity, exclusion, opportunity, and contract award data.

How to use SAM.gov MCP?

Requires a free SAM.gov API key from https://sam.gov (rotates every 90 days). Install via uvx or pip install sam-gov-mcp, then configure your MCP client (Claude Desktop, Codex, Gemini CLI, Copilot, etc.) with the JSON or TOML snippet provided in the README, setting the SAM_API_KEY environment variable.

Key features of SAM.gov MCP

• 19 tools covering entity, exclusion, opportunity, and award data
• Entity lookup by UEI, CAGE, or DUNS with registration status
• Exclusion checks by UEI/CAGE and search by name/agency/type
• Contract opportunity search with set-aside and NAICS filters
• Award search by PIID, vendor UEI, agency, NAICS, or fiscal year
• Federal hierarchy lookup and FFATA subaward reporting

Use cases of SAM.gov MCP

• Search for 8(a) and SDVOSB set-aside opportunities posted in the last 30 days
• Look up a contractor’s registration status, CAGE code, and primary NAICS
• Pull a vendor’s award history across all federal agencies
• Check a vendor list for active exclusions before issuing a purchase order
• Find IDIQ vehicles at a specific agency and NAICS to identify teaming opportunities

FAQ from SAM.gov MCP

What is required to run SAM.gov MCP?

A free SAM.gov API key from https://sam.gov, which rotates every 90 days. The server runs via uvx or as a Python package (sam-gov-mcp).

Which MCP clients are compatible?

Any local MCP client: Claude Desktop, Codex (ChatGPT), Gemini CLI, Copilot (VS Code), and others supporting local stdio servers (Claude Code, Cursor, Cline, Zed, Continue).

How is the server hardened?

Independently hardened across 6 live audit rounds against production SAM.gov endpoints, plus hypothesis-driven property tests. Pydantic models use extra="forbid" to surface API drift.

Where does the data come from?

All data comes from the public SAM.gov REST APIs. The server itself does not store any data; it fetches live information on each request.

What transport does SAM.gov MCP use?

It uses stdio transport (local subprocess). All configuration is passed via environment variables or client config files.