USA Spending MCP Server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@USA Spending MCP Server show me total spending by NASA in fiscal year 2024"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
USA Spending MCP Server
⚠️ DISCLAIMER: This is a proof of concept and is not intended for production use.
An MCP server for interacting with the USAspending.gov API, with optional login.gov authentication for cloud deployment.
Requirements
Python 3.11+
Related MCP server: federal-compass-mcp
Installation
Quick Install
uv tool install git+https://github.com/GSA-TTS/usa-spending-mcp-serverDevelopment Setup
git clone https://github.com/GSA-TTS/usa-spending-mcp-server
cd usa-spending-mcp-server
uv sync --devRunning Modes
The server supports two modes:
Mode | Command | Use Case |
stdio |
| Local use with Claude Desktop |
HTTP |
| Cloud deployment with login.gov auth |
Local Setup (Claude Desktop)
Get the installed tool path:
which usa-spending-mcp-serverAdd to your Claude MCP config (
~/.claude/claude_desktop_config.json):{ "mcpServers": { "usa-spending": { "command": "/path/to/usa-spending-mcp-server" } } }
HTTP Server with Login.gov Authentication
The HTTP server uses login.gov OIDC with PKCE for authentication, suitable for cloud.gov deployment.
Environment Variables
Variable | Required | Description |
| No | Set to |
| If auth enabled | Public URL of the server (e.g., |
| If auth enabled | Your login.gov application client ID |
| If auth enabled | Secret key for signing JWTs (generate with |
| No | OIDC discovery URL (defaults to login.gov sandbox) |
| No | Server port (default: |
Login.gov Setup
Register at partners.login.gov
Create a new OIDC application:
Protocol: OpenID Connect with PKCE (public client)
Redirect URI:
{BASE_URL}/auth/callback
Note your client ID for
LOGINGOV_CLIENT_ID
Running Locally
Without authentication (development):
uv run task devWith authentication:
export BASE_URL=http://localhost:8080
export LOGINGOV_CLIENT_ID=your-client-id
export JWT_SIGNING_KEY=$(python -c "import secrets; print(secrets.token_hex(32))")
uv run task dev-authCloud.gov Deployment
Set environment variables:
cf set-env usa-spending-mcp-server BASE_URL https://usa-spending-mcp.app.cloud.gov cf set-env usa-spending-mcp-server LOGINGOV_CLIENT_ID your-client-id cf set-env usa-spending-mcp-server JWT_SIGNING_KEY your-signing-keyDeploy:
cf push
Development
Available Tasks
uv run task dev # Run HTTP server without auth
uv run task dev-auth # Run HTTP server with auth
uv run task lint # Check code with ruff
uv run task lint-fix # Fix linting issues
uv run task format # Format code with ruff
uv run task test # Run tests
uv run task test-cov # Run tests with coverage
uv run task ci # Run all CI checksCode Quality
This project uses ruff for linting and formatting.
LLM-Based Evals (Optional)
For local testing of tool behavior using mcp-evals:
cd evals
npm install
ANTHROPIC_API_KEY=your-key npm run evalSee evals/README.md for details.
Project Structure
src/
usa_spending_mcp_server/
server.py # stdio MCP server (Claude Desktop)
server_http.py # HTTP server with auth (cloud.gov)
auth.py # login.gov OIDC authentication
tests/ # Python unit tests
evals/ # LLM-based evals (optional)
manifest.yml # cloud.gov deployment config
pyproject.tomlAvailable Tools
3 toolsexecuteB
Chain await call_tool(...) calls in one Python block; prefer returning the final answer from a single block.
Use return to produce output.
Only call_tool(tool_name: str, params: dict) -> Any is available in scope.
Inputs: code (required).
get_schemaA
Get parameter schemas for specific tools.
Use after searching to get the detail needed to call a tool.
Inputs: tools (required), detail. Returns: result
searchA
Search for available tools by query.
Returns matching tools ranked by relevance.
Inputs: query (required), tags, detail, limit. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
The three tools (execute, get_schema, search) have clearly distinct purposes: search finds tools, get_schema retrieves parameter details, and execute runs tools. No overlap.
All tools use lowercase verbs, which is consistent. However, the pattern varies: 'execute' is a standalone verb, while 'get_schema' and 'search' combine verb and noun. Minor deviation from a strict pattern.
With only 3 generic meta-tools and no domain-specific tools for USA Spending, the tool count is extremely insufficient for the server's purported purpose. It should have at least basic query tools for spending data.
The server claims to be about USA Spending but provides no tools to access spending data. The entire domain surface is missing, making it severely incomplete.
Maintenance
Related MCP Connectors
USAspending MCP — Federal spending data from USAspending.gov API
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
MCP server for Modern Treasury — payment orders, transactions, counterparties and ledgers.
Related MCP Servers
- AlicenseBqualityBmaintenanceMCP server for integrating Actual Budget with Claude and other LLM assistants.17494 npm287TypeScriptMIT
- AlicenseAqualityCmaintenanceAn MCP server that connects Claude to the USAJobs API, enabling natural language search for federal jobs, translation of government jargon, CV qualification analysis, and explanation of federal concepts like GS grades and clearances.1073 npm12MIT
- AlicenseAqualityDmaintenanceRead-only MCP server for exploring US federal spending data via the USAspending.gov API, enabling natural language queries on awards, agencies, recipients, and spending trends.12MIT
- AlicenseNot gradedqualityDmaintenanceA free, key-less MCP server for querying U.S. federal spending data from USAspending.gov, including contracts, grants, loans, recipients, agencies, and geographic breakdowns.MIT