Govtoolspro MCP Server runs on your own machine — the client starts it, so there is no endpoint to ping. 59 installs a week from npm. Last commit 12 Jun 2026.
Workflow tools for federal contractors: go/no-go scoring, incumbent intel, recompete, NECO.
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
# Placeholder so build/CI validators can complete the protocol handshake. The # server uses lazy config and starts without a real key; any actual tool call # requires the user's GOVTOOLSPRO_API_KEY (supplied at runtime) and would fail # auth at the backend otherwise. ToolHive in…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add govtoolspro-mcp-server -e 'GOVTOOLSPRO_API_KEY=<GOVTOOLSPRO_API_KEY>' -- npx -y govtoolspro-mcp-server
{
"mcpServers": {
"govtoolspro-mcp-server": {
"command": "npx",
"args": [
"-y",
"govtoolspro-mcp-server"
],
"env": {
"GOVTOOLSPRO_API_KEY": "<GOVTOOLSPRO_API_KEY>"
}
}
}
}
[mcp_servers.govtoolspro-mcp-server]
command = "npx"
args = ["-y", "govtoolspro-mcp-server"]
env = { GOVTOOLSPRO_API_KEY = "<GOVTOOLSPRO_API_KEY>" }
{
"mcpServers": {
"govtoolspro-mcp-server": {
"command": "npx",
"args": [
"-y",
"govtoolspro-mcp-server"
],
"env": {
"GOVTOOLSPRO_API_KEY": "<GOVTOOLSPRO_API_KEY>"
}
}
}
}
{
"servers": {
"govtoolspro-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"govtoolspro-mcp-server"
],
"env": {
"GOVTOOLSPRO_API_KEY": "<GOVTOOLSPRO_API_KEY>"
}
}
}
}
Put your own value in place of
<GOVTOOLSPRO_API_KEY> (API key from the GovToolsPro extension → Profile → API Keys tab. Format: gtp_live_... or gtp_test_).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
GOVTOOLSPRO_API_BASE (Override the API base URL. Default: https://mcp.govtoolspro.com/api/v1/workflows).
56+ AI tools for CRM, content, workflows, SkillForge & marketing automation.
Competitive intelligence - track what competitors ship each week. 8 tools, 3 prompt workflows.
GoHighLevel MCP for Claude: 250 tools, 51 modules, including a workflow builder
Open-source MCP server for PrismHR. PEO workflow tools + Microsoft 365 connectors.
Connect LLM tools to your Algolia account with user-scoped access for internal workflows.
Policy-gated x402 MCP for agent workflows with TEE receipts, 18 tools, and no custody.
Workflow planning, recovery checkpoints, coordination, fixtures, and compatibility tools for agents.
SEO tools for keywords, SERP, rankings, site audits, search analytics and content workflows.
Answers built from our own checks of this server.