Aegis Gov Contracts vs Midwest Legal Docs
A side-by-side look at the Aegis Gov Contracts and Midwest Legal Docs MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Aegis Gov Contracts for search & data extraction work over a hosted endpoint; choose Midwest Legal Docs for legal. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Aegis Gov Contracts when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
search_opportunities, get_opportunity_details, analyze_bid_potential.
Choose Midwest Legal Docs when
- You need dedicated capabilities in the Legal domain.
- You have the keys it needs:
MLD_AGENT_API_KEY, PORT, ALLOWED_HOSTS.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Legal |
| Quality signal | 49/100 · Fair | 29/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | MLD_AGENT_API_KEYPORTALLOWED_HOSTS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Aegis Gov Contracts | View Midwest Legal Docs |
Tools & capabilities
Aegis Gov Contracts tools 3
search_opportunitiesSearch active SAM.gov contracts by keyword, NAICS, agency, value rangeget_opportunity_detailsFull contract details, contacts, deadlines by notice IDanalyze_bid_potentialAI bid/no-bid analysis with score, strengths, risks
Midwest Legal Docs tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Aegis Gov Contracts
{
"mcpServers": {
"aegis-gov-contracts": {
"url": "https://aegisgov-contracts-mcp.vercel.app/mcp"
}
}
}
Midwest Legal Docs
No confirmed install command for Midwest Legal Docs yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Aegis Gov Contracts is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. Midwest Legal Docs belongs to Legal and uses an install path we have not confirmed yet. Pick Aegis Gov Contracts for search & data extraction work and Midwest Legal Docs for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Midwest Legal Docs has no confirmed install command yet — follow its own setup instructions.
Aegis Gov Contracts has no declared pricing — check the project's own site. Midwest Legal Docs has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add aegis-gov-contracts and midwest-legal-docs as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Aegis Gov Contracts has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 2 GitHub stars. Midwest Legal Docs has 29/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.
