MCP tool reference & install
Every install path, and all 53 tools with what each one does. For the philosophy behind why this exists, and how the tools group by GovCon lifecycle stage, see the MCP overview.
Every install path, and all 53 tools with what each one does. For the philosophy behind why this exists, and how the tools group by GovCon lifecycle stage, see the MCP overview.
Same install command everywhere; only the config path changes per client. Python 3.10+ required.
Installs to ~/.local/bin/govconapi-mcp, outside sandboxed folders like Documents.
14-day free trial at govconapi.com (no credit card). After trial: $19/mo Developer plan or $79/mo Pro. MCP is included with any paid plan.
Edit the config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": {
"govconapi": {
"command": "govconapi-mcp",
"env": {
"GOVCONAPI_KEY": "gca_your_key_here"
}
}
}
}
Quit and reopen Claude Desktop. The govconapi tools appear in the tool picker.
One command adds it for your user:
Or edit ~/.claude/settings.json manually using the same JSON as Claude Desktop.
Settings > Cursor Settings > MCP > Add new MCP server.
Or edit ~/.cursor/mcp.json directly:
{
"mcpServers": {
"govconapi": {
"command": "govconapi-mcp",
"env": { "GOVCONAPI_KEY": "gca_your_key" }
}
}
}
Install Continue in VS Code, then edit ~/.continue/config.yaml:
mcpServers:
- name: govconapi
command: govconapi-mcp
env:
GOVCONAPI_KEY: gca_your_key
Assistant panel > MCP Servers > Add Context Server. Or edit ~/.config/zed/settings.json:
{
"context_servers": {
"govconapi": {
"command": "govconapi-mcp",
"env": { "GOVCONAPI_KEY": "gca_your_key" }
}
}
}
Spawn the MCP server as a subprocess using the official mcp client SDK:
# pip install mcp from mcp import ClientSession, StdioServerParameters from mcp.client.stdio import stdio_client params = StdioServerParameters( command="govconapi-mcp", env={"GOVCONAPI_KEY": "gca_your_key"} ) async with stdio_client(params) as (read, write): async with ClientSession(read, write) as session: await session.initialize() tools = await session.list_tools() result = await session.call_tool( "search_opportunities", {"naics": "541330", "limit": 10} )
Works with any LangChain / LlamaIndex / custom agent that supports MCP tool adapters.
The govconapi-mcp package is a thin Python wrapper around our REST API, organized by GovCon lifecycle stage rather than by internal API module. Your AI client spawns it as a local subprocess over stdio. The subprocess reads GOVCONAPI_KEY from its environment, proxies each tool call to https://govconapi.com/api/v1/... over HTTPS, and returns structured JSON, the same shape you'd get calling the REST API directly.
Because it wraps the REST API, everything else carries over automatically: your rate limits, plan restrictions, filter validation, and request logging. Usage shows up in your normal account dashboard.
Open source on PyPI under MIT. Audit it, fork it, run it locally with your own API key.
Grouped by lifecycle stage, with every parameter, its type, and whether it's required. Expand a tool for its full signature.
13 tools are badged Pro: they return a 402 on the Developer plan. 4 more work on Developer but note where specific fields or filters are Pro-only. The other 36 have no plan distinction.
Common questions. If something isn't here, email [email protected].
No. MCP access itself is included with the Developer ($19/mo) and Pro ($79/mo) plans, same API key, same rate limits, and the 14-day free trial includes it too. What differs by plan is which of the 53 tools you can call, not access to MCP itself, see the next question.
13 of 53, badged Pro in the table above, return a 402 on Developer: the Companies cluster, Teaming Partners, Contacts, Vendor Risk, Recompete Watchlist, vehicle holders, and per-solicitation protest detail. 4 more work on Developer, with a note under each naming exactly which fields or filters are Pro-only. The other 36 have no plan distinction.
53, spanning Market Research, Opportunity Discovery, Capture & Teaming, Bid & Proposal/Negotiate, and Award & Compliance. See the table above.
Yes, all of them. MCP is an open standard, any client that speaks it works identically. See the install section above for each client's config file path.
Each tool call from your AI counts as one API call against your plan's limits, same as the REST API. The current per-plan limits are on the pricing page. You won't hit them with normal interactive use.
SAM.gov opportunities and exclusions, FPDS/USAspending prime contracts and subawards, GSA wage determinations and labor rates, SBA DSBS small-business certifications, and the federal agency organization tree. All 53 tools proxy the same REST API this site runs on, so coverage matches it exactly.
Most common cause: the binary is inside a sandboxed folder (~/Documents). Claude Desktop can't spawn processes from there. Use pipx install govconapi-mcp instead of a manual venv, it puts the binary at ~/.local/bin/ which sandboxes can reach. Check the log at ~/Library/Logs/Claude/mcp-server-govconapi.log for details.
The key lives in your local client's config file. It's sent over HTTPS in the Authorization header on each call. The MCP server never logs, transmits, or exposes it anywhere else. Source code is public and auditable on PyPI.
Yes. Query parameters like uei, naics, and piid work the same way across most tools, and each tool's docstring states exactly which of its response fields feed into which other tool's parameters. See the composability section on the overview page.
Model Context Protocol, an open standard from Anthropic that lets AI assistants call external tools. Think of it as “the API protocol for AI”. When you install an MCP server, your AI gains new capabilities. Ours gives it 53, spanning the federal contracting lifecycle.
Email [email protected]. The MCP server is open source, PRs welcome. We ship updates fast because it's a thin wrapper over the REST API.
Grab a 14-day trial key (no credit card), paste one JSON block into your Claude / Cursor / VS Code config, and ask your assistant a question about federal contracts. The same key works for the REST API too.
Get an API key • Jump to install • Why we built this • See pricing