Connect SAM.gov to Gemini Enterprise
Query SAM.gov directly from Gemini Enterprise. Arlet links the two through one MCP connection and takes care of API keys.
This server connects your AI client to SAM.gov, the US government's official system for contract opportunities and entity registrations, operated by the GSA.
Key features:
- search_opportunities: find active and past contract notices - solicitations, pre-solicitations, combined synopses, sources-sought and award notices - filtered by title keyword, NAICS code, procurement type, agency, place-of-performance state and posted-date range. The posted range defaults to the last 90 days and is capped at one year by the upstream API; dates are accepted in ISO form and converted to SAM.gov's MM/dd/yyyy automatically.
- search_entities: look up companies and organizations registered to do business with the US government, by legal name, 12-character UEI or 5-character CAGE code. Returns registration status and expiration, address, and identifiers.
The UEI returned by search_entities is the same identifier USAspending uses for award recipients, so the two servers join cleanly: find a company here, then pull its award history there. Division of labor with USASpending: SAM.gov is where notices are published (before and at award); USAspending is where actual spending is recorded.
Using the API requires a personal API key generated from your SAM.gov account's Account Details page (a login is required; keys are tied to the account's roles). Set it as SAM_GOV_API_KEY in your Arlet environment variables. Note the upstream gateway answers invalid keys with an empty 404 response; this server converts that into an actionable error message.
How to connect SAM.gov to Gemini Enterprise
- 1
In the Arlet dashboard, open Data tools, find SAM.gov, set the API key issued by SAM.gov and switch it on.
- 2
Sign in to Gemini Enterprise with your organization Google account and open the gear icon at the bottom left → Connectors → Add MCP Server.
- 3
In the MCP info tab, enter https://mcp.arlet.dev/mcp/ as the Server URL and "Arlet" as the Name. In the Auth tab, enter the OAuth settings from the Arlet docs (Authorization URL / Token URL / Client ID / Client Secret / Scopes) and click Add.
- 4
In the connector list on the chat screen, click Connect on Arlet, sign in with Google and authorize. Arlet can then be enabled with the toggle.
Adding custom connectors (MCP) requires a Gemini Enterprise subscription and is not available in the consumer Gemini app. See the docs for the values to enter in the Auth tab.