GovToolsPro MCP Server

An MCP server that gives Claude (and any MCP client) workflow tools for federal contractors — not raw data access, but decisions: go/no-go scoring, incumbent intelligence, teaming-partner search, recompete prediction, Navy NECO lookup, SAM.gov solicitation retrieval, and market intelligence (labor rates, award patterns, market analysis).

It wraps the live GovToolsPro API. You bring an API key; the server proxies your calls.

Tools

| Tool | Cost | What it does | |---|---|---| | balance | free | Credit balance + subscription status. | | get_solicitation | free | Notice ID (or solicitation number) → structured SAM.gov fields (NAICS, PSC, set-aside, place of performance, deadline, contacts, attachment links). The workflow entry point. | | score_go_no_go | free | Score a solicitation GO / NO-GO (0–100) against your company profile, with hard-blocker detection (CMMC, geographic, set-aside). | | find_incumbents | free | Identify the current incumbent via USAspending + FPDS, with competition signals and anticipated next-award date. | | find_partners_near | free | Rank nearby teaming partners / subcontractors by proximity for a place of performance. | | predict_recompete | free | Discover expiring contracts (recompete opportunities) by NAICS/PSC/state/value, enriched with option-exercise signals. | | lookup_neco_data | free | Parse a Navy NECO (neco.navy.mil) solicitation into structured fields. No other govcon MCP has this. | | lookup_labor_rates | free | Benchmark federal labor rates for a NAICS / labor category — GSA CALC awarded ceiling rates + BLS OEWS wages with a government wrap estimate. | | analyze_award_patterns | 3 credits | How contracts in a NAICS are awarded: award-size distribution, competition mix, bid intensity, contract vehicles, pricing types. | | analyze_market | 5 credits | Market-intelligence snapshot for a NAICS: 5-year spend trend, industry size, top contractors + HHI concentration, set-aside mix, geography, contract vehicles. |

Every tool returns decision-support output with a disclaimer — verify against the official solicitation before relying on results. Credits are drawn from the shared GovToolsPro pool (extension + API + connector all bill the same balance); free tools never deduct.

Install

Add to your MCP client config (Claude Desktop, Claude Code, Cursor, Cline, Zed, …):

{
  "mcpServers": {
    "govtoolspro": {
      "command": "npx",
      "args": ["-y", "govtoolspro-mcp-server"],
      "env": { "GOVTOOLSPRO_API_KEY": "gtp_live_..." }
    }
  }
}

Get an API key

Create a key in the GovToolsPro extension → Profile → API Keys tab (format gtp_live_... / gtp_test_...).

Use as a Claude connector (remote MCP)

Prefer not to run anything locally? GovToolsPro is also a hosted remote MCP server you can add to Claude as a connector — no install, no API key, sign in with your GovToolsPro account.

• Remote MCP URL: https://mcp.govtoolspro.com/api/mcp
• In Claude: Settings → Connectors → Add custom connector, paste the URL, and leave the OAuth fields blank (the server self-registers via Dynamic Client Registration).
• You'll be sent to auth.govtoolspro.com to sign in; Claude then connects over OAuth 2.1. Toggle the connector on in a conversation to use its tools.

The same 10 tools are available over the connector, billed against the same shared credit balance as the extension and the stdio package.

Configuration

| Env var | Required | Default | |---|---|---| | GOVTOOLSPRO_API_KEY | yes | — | | GOVTOOLSPRO_API_BASE | no | https://mcp.govtoolspro.com/api/v1/workflows |

Local development

npm install
npm run build

# end-to-end stdio smoke test against the live API
GOVTOOLSPRO_API_KEY=gtp_test_... npm run smoke

To point a client at your local build:

{
  "command": "node",
  "args": ["/absolute/path/to/govtoolspro-mcp-server/dist/index.js"],
  "env": { "GOVTOOLSPRO_API_KEY": "gtp_test_..." }
}

Notes

• Workflow MCP, not a data wrapper. Competing govcon MCPs return raw SAM.gov/FPDS JSON; these tools return synthesized decisions.
• CUI safety. The API rejects content with CUI / FOUO / Distribution-Statement markings; those rejections surface to the client as clear errors. Do not submit controlled content.
• No warranty. Output is decision support only — not legal, contractual, or award-outcome advice.

Troubleshooting

| Symptom | Cause / fix | |---|---| | Out of credits / 402 | Three tools are metered (analyze_market 5, analyze_award_patterns 3). Check balance, or top up at govtoolspro.com. Free tools never deduct. | | Connector keeps asking you to sign in / 401 | The remote connector requires OAuth — complete sign-in at auth.govtoolspro.com, then toggle the connector on in the conversation ("Search and tools"). | | No data for this NAICS (502) | That NAICS has no federal activity in the window — you are not charged. Try a broader NAICS or fewer filters. | | CUI rejection error | The API rejects content marked CUI / FOUO / Distribution-Statement. Remove controlled content and retry. | | get_solicitation returns nothing | Use the 32-char notice ID from the sam.gov/opp/<id>/view URL. Some archived/cancelled notices may be unavailable. | | Invalid API key (stdio) | Ensure GOVTOOLSPRO_API_KEY is a gtp_live_… / gtp_test_… key from the extension's Profile → API Keys tab. |

License

MIT © Michael Smyth