Compatible with every major AI agent and IDE
What is the GovInfo (GPO Legislative Docs) MCP Server?
Connect your AI agent to the GovInfo API by the U.S. Government Publishing Office (GPO) to research and retrieve official federal documents through natural conversation.
What you can do
- Explore Collections — List all available document categories like Congressional Bills, the Federal Register, and Presidential Papers
- Advanced Search — Use Lucene syntax to perform complex queries across the entire GPO database for specific keywords or topics
- Document Retrieval — Fetch detailed metadata, summaries, and historical context for specific legislative packages
- Content Access — Retrieve document content in multiple formats including PDF, XML, and MODS for deep analysis
- Date-based Filtering — Track legislative changes and new publications by listing packages within specific timeframes
How it works
- Subscribe to this server
- Enter your GovInfo (Data.gov) API Key
- Start querying official government data from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Legal Professionals — quickly find specific bill versions, federal regulations, or court opinions without manual portal navigation
- Researchers & Journalists — track government activity, historical records, and policy changes using automated queries
- Policy Analysts — monitor legislative progress and federal notices in real-time to stay ahead of regulatory shifts
Built-in capabilities (6)
Get metadata for a specific GovInfo collection
Note: Binary formats like pdf or zip will be returned as raw text/binary strings. Download or retrieve GovInfo package content
Get detailed metadata for a specific GovInfo package
g., Congressional Bills, Federal Register). List all available GovInfo document collections
List packages within a GovInfo collection by date
Search GovInfo collections
Why CrewAI?
When paired with CrewAI, GovInfo (GPO Legislative Docs) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call GovInfo (GPO Legislative Docs) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
GovInfo (GPO Legislative Docs) in CrewAI
GovInfo (GPO Legislative Docs) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect GovInfo (GPO Legislative Docs) to CrewAI 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 GovInfo (GPO Legislative Docs) in CrewAI
The GovInfo (GPO Legislative Docs) 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 6 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI 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
GovInfo (GPO Legislative Docs) for CrewAI
Every tool call from CrewAI to the GovInfo (GPO Legislative Docs) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I search for specific keywords across all government documents?
Yes! Use the search_govinfo tool with Lucene syntax to perform complex queries. You can filter by date, collection, or specific fields to find exactly what you need.
How do I get the actual text or PDF of a bill?
Use the get_package_content tool with the specific packageId and choose your preferred format (pdf, xml, mods, etc.) to retrieve the document content.
What types of document collections are available?
Run the list_collections tool to see all available sources. Common codes include 'BILLS' for Congressional Bills, 'FR' for the Federal Register, and 'CPD' for Compilation of Presidential Documents.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Insightful
10 toolsManage employee productivity, time tracking, and activity via Insightful API.

ClientSuccess
6 toolsReduce churn and grow accounts with health scoring, engagement tracking, and success playbooks built for customer success teams.

FindThatLead
12 toolsUncover business email addresses from domain names and LinkedIn profiles to fuel your outbound prospecting pipeline.

RudderStack
7 toolsConnect your AI assistant natively to RudderStack to effortlessly monitor global data sources, trace routing connections, and audit enterprise marketing audiences via structured text commands.
