Bring Federal Procurement
to VS Code Copilot
Learn how to connect DOD Contracts (FPDS) to VS Code Copilot and start using 1 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the DOD Contracts (FPDS) MCP Server?
Connect your AI agent to the Federal Procurement Data System (FPDS) to monitor government spending and analyze contract awards in real-time.
What you can do
- Contract Search — Query the massive database of federal procurement actions using standard FPDS search syntax.
- DOD Targeting — Specifically isolate Department of Defense data by filtering for Department ID '9700' or Agency Code '9700'.
- Market Intelligence — Track vendor performance, identify upcoming procurement trends, and analyze historical spending patterns.
- Pagination Support — Navigate through large result sets using the start parameter to fetch data in batches of 10.
How it works
- Subscribe to this server
- Configure your access identifier
- Start querying federal contracts from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Government Contractors — monitor competitors and find new opportunities within the DOD.
- Data Analysts — extract raw XML contract data for spending analysis and reporting.
- Journalists & Researchers — track government transparency and public spending across federal agencies.
Built-in capabilities (1)
To target DOD contracts, include DEPARTMENT_ID:"9700" or AGENCY_CODE:"9700" in the sQuery parameter. Returns XML data containing contract entries. Search federal contracts via FPDS Atom Feed
Why VS Code Copilot?
GitHub Copilot Agent mode brings DOD Contracts (FPDS) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 1 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
DOD Contracts (FPDS) in VS Code Copilot
DOD Contracts (FPDS) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect DOD Contracts (FPDS) to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for DOD Contracts (FPDS) in VS Code Copilot
The DOD Contracts (FPDS) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 1 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
DOD Contracts (FPDS) for VS Code Copilot
Every tool call from VS Code Copilot to the DOD Contracts (FPDS) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I specifically target Department of Defense (DOD) contracts?
To target DOD contracts, include DEPARTMENT_ID:"9700" or AGENCY_CODE:"9700" in your sQuery parameter when using the search_contracts tool.
Can I paginate through large sets of contract results?
Yes. The search_contracts tool supports a start parameter. Results are returned in batches of 10, so you can increment the start number (e.g., 10, 20, 30) to see more records.
What search syntax should I use for the sQuery parameter?
The search_contracts tool uses the standard FPDS Atom Feed search syntax. You can search by keywords, or use specific fields like VENDOR_NAME:"Example Corp" or PIID:"ContractID".
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
AudioStack
10 toolsProduce end-to-end AI audio via AudioStack — automate high-quality speech, mixing, and mastering via AI.
Personio Alternative
25 toolsAutomate HR operations via Personio — manage employee records, track attendance, handle absences, and streamline recruiting directly from any AI agent.
UpGuard
9 toolsMonitor your attack surface and assess vendor security risks with continuous scanning that identifies vulnerabilities before attackers do.
Brevo
11 toolsEngage customers across email, SMS, and chat with marketing campaigns and transactional messaging that scale with you.