HigherGov MCP
Overview
HigherGov’s MCP allows subscribers to access HigherGov's comprehensive federal and state and local data directly inside supported AI assistants and LLM tools for search, research, and analysis.
MCP stands for Model Context Protocol. It is a standard way for AI assistants to securely connect to external tools and data sources. With the HigherGov MCP, an LLM can search HigherGov opportunities, awards, contractors, documents, NSNs, and related records using natural language.
The HigherGov MCP is powered by the HigherGov API. Each subscription includes 10,000 records per month, which will be sufficient for the vast majority of use cases.
HigherGov MCP endpoint:
https://www.highergov.com/mcp/Creating a HigherGov API Key
API keys can be managed when signed in to HigherGov from the API Management screen (requires Admin access).
Or navigate manually:
Sign in to HigherGov.
Select the gear icon in the upper-right corner.
Select API.
Click Generate Key.
Copy and securely save the key.
Important: the full API key is only displayed once when it is created. Make sure to copy and securely store it before leaving the page.
Authentication
The preferred authentication method is to send your HigherGov API key as a bearer token:
Some MCP clients support custom headers directly. If your client does, use the bearer-token method above.
If your LLM does not support bearer tokens, you can also pass the api_key as a parameter when setting the MCP endpoint.
Connecting to HigherGov MCP
MCP support is changing quickly across LLM providers. The exact setup steps may change, so always check your LLM provider’s latest MCP or connector documentation.
At a high level, setup usually works like this:
Open your AI assistant’s MCP, Connector, App, or Tools settings.
Add a new remote MCP server.
Enter the HigherGov MCP endpoint:
4. Set authentication using your HigherGov API key:
Save or scan tools.
Start asking questions naturally.
Example prompts:
Claude
Claude supports custom connectors using remote MCP servers. In Claude, custom connectors can be added from Settings → Connectors, where users can enter the remote MCP server URL. Team and Enterprise administrators may also manage custom connectors through admin connector settings. (claude.com)
Use:
Authentication:
General steps:
Open Claude.
Go to Settings → Connectors.
Select Add custom connector.
Enter the HigherGov MCP URL.
Add authentication if supported by your Claude plan/client.
Enable the connector in a chat.
Claude allows connectors to be enabled or disabled per conversation from the chat interface. (claude.com)
OpenAI / ChatGPT
OpenAI supports remote MCP servers through ChatGPT apps/connectors and through the OpenAI API. Remote MCP servers are servers available over the public internet that implement MCP. (platform.openai.com)
For ChatGPT, custom MCP apps are managed through Developer Mode for eligible workspaces. OpenAI’s current help documentation describes availability for ChatGPT Business, Enterprise, and Edu workspaces, with admins or authorized developers able to create and test custom MCP apps. (help.openai.com)
Use:
Authentication:
General steps:
Confirm your workspace supports custom MCP apps/connectors.
Enable Developer Mode if required.
Create a new custom app/connector.
Provide the HigherGov MCP endpoint.
Configure authentication using your HigherGov API key.
Scan tools.
Test the app in a new chat.
Publish or enable it for your workspace if desired.
For API usage, configure HigherGov as a remote MCP server using the HigherGov MCP endpoint and bearer authorization. OpenAI’s Responses API supports remote MCP servers using a server_url, and authorization may be supplied depending on the server. (platform.openai.com)
Example shape:
Gemini
Gemini CLI supports MCP servers through settings.json or the gemini mcp add command. Gemini CLI supports stdio, SSE, and Streamable HTTP transports; for HigherGov, use the HTTP transport. (github.com)
Use:
Add with CLI command
Verify the connection:
Gemini CLI also provides an /mcp command inside the CLI to show configured servers, connection status, available tools, and discovery status. (github.com)
Or configure settings.json
settings.jsonMCP Tools and Common Use Cases
The HigherGov MCP exposes tools that let your AI assistant search HigherGov data and retrieve supporting records.
You do not need to know the tool names to use the MCP. In most cases, you can ask questions naturally and the LLM will choose the appropriate tool.
Opportunity Search
Tool: search_opportunities
Use this to find and identify relevant opportunities, including:
Federal contract opportunities
State and local contact opportunities
Federal grant opportunities
DIBBS opportunities
Federal forecasts
SLED forecasts
Common use cases:
Find active opportunities that match your products or services.
Identify opportunities by market, NAICS, customer, or topic.
Search federal and state/local opportunities together.
Forecast upcoming opportunities using federal forecasts and SLED forecasts.
Use a saved HigherGov search to monitor opportunities.
Find relevant opportunities and then retrieve the solicitation documents.
Example prompts:
Opportunity Documents
Tool: get_opportunity_documents
Use this to retrieve documents and extracted text for an opportunity.
Common use cases:
Summarize solicitation documents.
Extract requirements from an RFP or RFQ.
Review attachments for due dates, submission instructions, evaluation criteria, or scope.
Pull document text for an opportunity found through opportunity search.
Example prompts:
Awards Research
Tools:
search_federal_contractssearch_federal_idvssearch_federal_grantssearch_federal_subcontractssearch_federal_subgrants
Use these tools to research historical awards, spending, recipients, contract vehicles, and subcontract/subgrant activity.
Common use cases:
Research prior federal contract awards in a market.
Find likely incumbents or competitors.
Search IDVs, GWACs, BPAs, IDIQs, and other federal contract vehicles.
Research federal grant awards by topic, recipient, or program.
Analyze subcontract or subgrant activity involving a company.
Understand historical buying patterns before pursuing an opportunity.
Example prompts:
Contractor and Partner Research
Tools:
search_awardeesget_awardee_detail
Use these tools to find and research companies, including potential teaming partners.
Common use cases:
Find potential partners for an opportunity or market.
Identify contractors by capability, NAICS, UEI, or CAGE.
Find a company’s UEI or CAGE code.
Review contractor profiles, registrations, NAICS codes, PSC codes, business types, and capabilities.
Research agency experience, vehicles, and subcontract relationships.
Compare potential partners or competitors.
Example prompts:
NSN / DIBBS Research
Tool: search_nsn
Use this to search NATO Stock Number and DIBBS-related data.
Common use cases:
Look up an NSN.
Find suppliers by CAGE code.
Search by part number.
Review recent supplier and award history for an NSN.
Example prompts:
Last updated