You stay in control
The connection uses OAuth 2.1 and requires your explicit approval. You see exactly which permissions are requested before anything is granted.
Beta
Connect your AI agent to federal contracting data. Ask about opportunities, awards, incumbents, spending, and vendors in plain language, and get answers drawn from GovChime with links back to the records behind them.
Paste this into Claude, Codex, or Claude Code and it will configure the connection itself.
Fetch and execute the appropriate instructions to set me up for GovChime from https://www.govchime.com/agent-setup/prompt.md
A read-only server built on the Model Context Protocol, the open standard that lets AI agents connect to external services. Add it once to your agent, sign in with your GovChime account, and the agent can answer procurement questions directly from GovChime data.
It is not a download and it never distributes an API key. There is nothing to install and no secret to paste into your agent's configuration.
The connection uses OAuth 2.1 and requires your explicit approval. You see exactly which permissions are requested before anything is granted.
Your GovChime browser session is never sent to the AI client. It receives a separate token bound to the MCP endpoint, which cannot be used against the website or the API.
Every tool reads. None writes. The connection cannot change your account, your saved work, or any GovChime record.
Your agent picks these itself — you do not call them by name. They are listed so you can see what the connection covers, and so a tool your agent reports matches something here.
search_opportunitiesget_opportunityfind_similar_opportunitiesfind_recompetesget_spending_leaderboardget_spending_trendssearch_contract_awardsget_contract_awardget_award_relationshipsget_opportunity_incumbentget_vendor_profilesearch_vendorsget_vendorlookup_agencylookup_naicslookup_psclookup_codessearchfetchAsk in plain language. A keyword is optional, so a question made only of filters is valid on its own.
“What opened in my NAICS last week that is still accepting bids?”
Resolves the industry to codes, filters by posting date and open status, and reports each response deadline.
“Who are the biggest vendors at DHS for IT services in FY2025?”
Resolves the agency to the right identifier, then aggregates obligations rather than listing awards — so the totals are real period spending.
“Who currently holds this contract?”
Runs incumbent resolution and states how firm the answer is: a named prior award, an inferred candidate, or nothing.
“Is spending in this market growing or shrinking?”
Returns a fiscal-period series and flags the year still in progress, so a year-to-date figure is not compared against a completed one.
“What work at this agency is expiring in the next six months?”
Lists awards whose period of performance ends inside the window, with the vendor and the expiry date.
“What else does this company hold, and who do they compete with?”
Builds a vendor profile from award history, vehicles, and overlapping industries and agencies.
By role, for teams deciding whether this fits how they already work.
Filter opportunities by publication date, so a standing weekly sweep returns exactly what appeared since the last one — narrowed to your NAICS codes, agencies, or set-aside programs.
Response deadlines are a separate filter from publication dates. Ask what closes in the next fourteen days without pulling in everything merely posted recently.
The active filter drops solicitations once their response deadline is more than a day past, so a pipeline list does not fill up with expired work. Each result carries its own deadline, because a notice that closed earlier today is still listed, and notices published without a deadline stay open.
Filter by individual programs such as 8(a), HUBZone, SDVOSB, and WOSB, or by a program group that expands to every member code at once.
Vendor records distinguish formally awarded certifications from self-reported business characteristics, so the two are never conflated.
Search awards by agency, industry, or vendor to see who currently holds the work, what was obligated, and how the award has changed over its life.
Every search reports the full number of matching records independently of how many rows are returned, so counting does not mean paging through results.
Turn an industry description into NAICS codes before filtering, including sector ranges that are not valid as a plain numeric prefix.
Name a department or a component — including acronyms like DOD — and the agent gets back the identifier each search needs, so an agency filter never silently matches nothing.
Set-aside programs, notice types, and vendor certifications are closed lists. The agent can read the accepted values, including which programs a group code expands to.
Federal procurement data has distinctions that are easy to get wrong. The server states them to the agent so answers stay correct.
A solicitation is republished many times as it moves from Sources Sought through Solicitation to Award Notice. Results collapse those into one opportunity with a notice count, so six notices are never reported as six opportunities.
An award value is its lifetime total across every transaction, not the amount obligated in a filtered period. Spending within a period comes from transaction-level obligation deltas instead.
Fiscal years run October 1 to September 30 and are named for the year they end in. The year currently in progress is year-to-date and is not comparable to a completed year.
Vendors are keyed by the 12-character Unique Entity Identifier. DUNS numbers are not current identifiers.
NAICS classifies the industry of the supplier; PSC classifies the product or service being bought. They are separate filters and are never interchangeable.
Opportunities and awards come from different source systems and identify the same agency differently. The agent resolves a name to the right identifier for each search rather than guessing, which is what turns an agency question into real results.
8(a), HUBZone, SDVOSB, and WOSB are separate programs that are also small-business set-asides. Filtering on the general small-business group alone understates the total, so the agent is told to combine them.
Federal contract opportunities, contract awards, registered vendors, and the NAICS taxonomy. Grants and subawards are outside coverage.
Yes. The GovChime MCP server is built and maintained by GovChime and hosted by GovChime. There is no third-party connector.
Any agent that supports remote MCP servers over OAuth. Claude and Codex are supported today. Other agents can connect using the server URL once their callback and token-lifecycle requirements are reviewed.
No. There is no key to manage and none is ever distributed. You sign in with your existing GovChime account and approve the connection, which issues a short-lived token scoped to the MCP endpoint alone.
Read-only government contracting data: opportunities, awards, vendors, and the NAICS taxonomy. It cannot see your saved searches, favorites, alerts, billing, or account settings, and it cannot create, edit, or delete anything.
No. Your conversation history stays in your AI agent. GovChime receives only the individual tool calls the agent makes.
No. Your browser session stays in your browser. The client receives a separate token that is bound to the MCP endpoint and cannot be used against the GovChime website or API.
The access token is short-lived, but your agent is also given a refresh token and renews in the background, so you stay connected without signing in again. Refresh tokens rotate on every use: presenting an old one retires the whole chain, which limits what a stolen token is worth.
Tell it the filter you want in plain language. Every search accepts date windows, lifecycle status, agency, industry, place of performance down to ZIP, set-aside program, and the value of the awarded contract, and a keyword is optional, so a filter-only question is valid on its own. Distance from a point is the exception: there is no radius search, so ask for the states or ZIP codes you mean.
Setup takes a server URL and a sign-in. Instructions for Claude, Claude Code, Codex, Cursor, and any other MCP-compatible agent are on the configuration page.
Configure your agentTool coverage and client support may change while the server is in beta. Tokens expire on their own, and revoking a connection takes effect immediately for every token in that connection.