Regulations.gov MCP for AI. Track US Federal Rules and Public Input.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
Regulations.gov (eRulemaking) lets your AI agent navigate the complex US federal rulemaking process. Connect to this server to search for rules, analyze public comments, and track dockets from agencies like the EPA and FAA.
You get direct access to official government records, allowing you to monitor legislative changes without manually checking hundreds of agency portals.
What your AI can do
Get comment
Retrieves full details for one specific public comment submission.
Get docket
Gets the complete record and supporting materials for a known rulemaking docket folder.
Get document
Fetches all details about a specific rule, notice, or proposed document ID.
Find rules, notices, and proposed regulations by keywords, date, or agency ID.
Get complete details for a specific rulemaking docket folder.
Find and analyze public feedback submitted to federal agencies based on criteria.
Pull the full details for one document ID you already know about.
Fetch all specific information associated with a single public comment.
Ask an AI about this
Waiting for input…
Regulations.gov (eRulemaking) MCP Server: 6 Tools for Compliance Data
Use these tools to search, retrieve, and analyze federal documents, dockets, and public comments from across US government agencies.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Regulations.gov (eRulemaking) on VinkiusGet Comment
Retrieves full details for one specific public comment submission.
Get Docket
Gets the complete record and supporting materials for a known rulemaking docket...
Get Document
Fetches all details about a specific rule, notice, or proposed document ID.
Search Comments
Searches and filters public comments based on keywords or date ranges across...
Search Dockets
Finds general information about rulemaking dockets using search criteria like agency...
Search Documents
Searches for any official document type (rules, notices) across the federal database.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Regulations.gov integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Regulations.gov (eRulemaking), then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Regulations.gov. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 6 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Tracking regulations shouldn't feel like detective work.
Today, tracking a single regulatory change means logging into the EPA portal for notices, then going to the Federal Register for proposed rules, and maybe checking an independent government site just for public comments. You spend hours copying IDs and pasting them across tabs just to build one timeline.
With this MCP server, you let your AI agent do the heavy lifting. Instead of manual cross-referencing, you run `search_dockets`, which aggregates the entire history—the rules, the notices, and all public input—into a structured data payload.
Regulations.gov MCP Server: Get verifiable policy context.
You eliminate manual searches for document IDs. You don't have to know if you need the 'notice' or the 'final rule'; your agent finds it using `search_documents` and gives you immediate access via `get_document`.
What changes is that you get verifiable, machine-readable context instantly. No more guesswork about which version of a rule was active when.
What your AI can actually do with this
Listen up. If you're wading through federal regulations—the kind of stuff coming out of the EPA or the FAA—you need your AI agent hooked directly into Regulations.gov. This server lets you bypass manually checking a dozen different agency websites; you get straight access to official, structured government records that track everything from initial notices to finalized rules and every single public comment attached to them.
When you connect this MCP Server, your agent handles the heavy lifting of navigating the entire U.S. federal rulemaking process. It’s not just a search box; it's a deep data pull for compliance work.
Discovery: Finding What You Need First
You gotta start by finding the right subject matter. If you don't know what rule or notice ID you're after, you can use search_documents. This tool lets your agent search across the entire federal database using keywords, specific date ranges, or even filtering by an agency ID to find any official document type—rules, notices, proposed regulations—that applies.
For broader context, if you need to know what dockets exist about a certain topic, use search_dockets. This finds general information on rulemaking folders based on criteria like the sponsoring agency name or the core subject matter. If your focus is public sentiment instead of the rule itself, search_comments lets your agent filter and search through public feedback using keywords or specific date ranges across multiple active dockets.
Deep Dives: Getting the Full Picture
Once you've found a general area, you need the specifics. If you know the exact docket folder number for a major rule change, get_docket pulls the complete record and all supporting materials associated with that rulemaking action—it’s everything.
If your agent finds a document ID from one of those searches, it can use get_document. This fetches every detail about that specific proposed rule, notice, or regulatory document, giving you metadata like when the comment period started or what modifications have happened to its status. If all you need is the raw text and context for one single public comment—say, from an industry group opposing a measure—get_comment retrieves the full details for that specific submission.
Tracking Public Feedback
Public comments are where the real signal is. Your agent doesn't just find them; it can analyze them. While search_comments lets you filter thousands of submissions by keywords or date, if you have a single comment ID, you use get_comment to pull every piece of information attached to that person's submission.
This gives you the full context for analyzing community sentiment on specific rules.
In short: If you need to find official documents like proposed regulations using keyword searches, run search_documents. To pinpoint general rulemaking activity by agency or topic, use search_dockets. For tracking public commentary based on keywords across multiple dockets, execute search_comments. When you're ready for the final data—whether it’s pulling the entire supporting file set using get_docket, fetching all metadata for a specific document ID with get_document, or retrieving every detail about one single piece of feedback via get_comment—you've got your answer.
This server handles the complexity; you just point your agent at the problem.
019e38e3-0bfb-7357-b1ea-052fed909d79 
Here's how it actually works
The bottom line is, your AI acts like a specialized regulatory analyst that queries government databases directly, instead of you manually browsing complex websites.
Subscribe to this server and enter your Regulations.gov API Key.
Your AI client (Claude, Cursor, etc.) sends a query using the specific tool function you need (e.g., search_documents).
The server runs the request against the federal database and returns structured data—like comment text or docket details—to your agent.
Who is this actually for?
Compliance officers and policy analysts use this when they need to prove what the law actually says. If you're tired of clicking through multiple agency websites just to track one rule change, this is for you. It pulls the raw data so your agent can do the heavy lifting.
Uses search_dockets and get_document to verify that internal processes align with federal requirements.
Runs search_comments to quickly map out public sentiment around proposed regulations before a policy launch.
Employs get_comment and get_docket to build an auditable trail of historical regulatory actions.
What Changes When You Connect
Audit Compliance: Instead of manually jumping between EPA, FAA, and CMS sites, use search_dockets to find all relevant docket folders. You get a single source of truth for every action taken on a rule.
Analyze Public Sentiment: Don't just read the headlines. Use search_comments to pull hundreds of public submissions. Your agent can then summarize whether industry feedback or citizen concerns dominate the discussion.
Deep Document Forensics: When you need to know when and how a rule changed, use get_document. This pulls deep metadata about modification history, which is crucial for compliance deadlines.
Instant Docket Access: Stop hunting through folder trees. Calling get_docket gives you the full context—all supporting documents and related materials—in one clean data payload.
Pinpoint Comments: Need to know what specific people thought about a rule? Use get_comment after finding the relevant document ID. You pull individual, verifiable feedback records.
See it in action
A Pharma Company Needs Compliance Proof
The compliance officer needs to know if a proposed rule affects their drug class. Instead of searching 10 different agency websites, the agent runs search_documents using key terms and the relevant date range. It then uses get_docket on the top result to pull all supporting materials for an audit trail.
Tracking Industry Opposition
A policy team wants to see how strongly industry groups feel about a new emission standard. They run search_comments targeting 'emission standards' and filter by 'industry.' This gives them a quantitative view of opposition that would take days to compile manually.
Researching Historical Regulatory Changes
A legal scholar needs the complete history for an old regulation. They use search_dockets to find the main folder, then call get_document repeatedly on specific IDs to map out every version and change over decades.
Monitoring a Specific Agency's Activity
You are watching a rival agency. You use search_documents to filter all activity by the competitor's ID, limiting results to the past week. This gives you an immediate alert on any new rules they might be proposing.
The honest tradeoffs
Treating Regulations like a general search engine
Trying to ask your agent, 'What are all the laws about cars?' and expecting it to return clean policy data. The system can't distinguish between law summaries and actual rule filings.
Start specific. Use search_documents with precise keywords (e.g., 'emissions standard') AND a date range, OR use search_dockets first to narrow the focus to one agency or topic area.
Assuming all data is in one place
Thinking that just calling get_document on an ID gives you the comments too. It only gets document metadata; you need separate tools for feedback.
Use a two-step process: First, use search_documents to find the main rule ID. Second, take that ID and feed it into search_comments or get_docket to grab all related context.
Ignoring the importance of dockets
Focusing only on a 'Final Rule' document without knowing what evidence led up to it. You miss the full process and potential counter-arguments.
Always start with search_dockets. The docket folder contains all supporting material—the rule, the notices, and the rationale—giving you the complete picture.
When It Fits, When It Doesn't
Use this server if your work requires verifiable data on US federal policy. You need to know what a government agency proposed, published, or responded to. Think compliance, law, or deep academic research.
Don't use it if you just need general information (like 'what is an emission standard?'). For simple definitions, look elsewhere. If your goal is simply to find one piece of text from a non-government source, this isn't the tool. Use this when the data needs provenance—when knowing which federal agency published it and who commented on it matters.
The flow should always be: search_dockets -> (find target) -> get_document or get_comment (for details).
Questions you might have
How do I find public comments for a specific document using search_comments? +
You need to use search_comments and provide the relevant keywords or ID. The tool filters through all submitted feedback, allowing you to analyze community sentiment without reading thousands of pages.
What's the difference between search_dockets and get_docket? +
search_dockets helps you find a folder by topic or agency. get_docket requires you to already have a specific docket ID, giving you the full contents of that single, defined rulemaking action.
Can I use get_document to see public comments? +
No. get_document retrieves details only about the document itself (like its metadata). You must use dedicated tools like search_comments or get_comment for actual public feedback.
I need to find all rules from the EPA last year; which tool should I use? +
You should start with search_documents. This allows you to filter by both the agency (EPA) and a specific time frame, giving you a list of relevant rule IDs.
How do I handle rate limits when running multiple `search_documents` queries? +
If you exceed the API call limit, the server returns a 429 error. Your agent should wait a specified cooldown period and retry the request using an exponential backoff strategy.
What parameters are required when I use the `get_comment` tool? +
You must provide the unique Comment ID and the associated Document ID. The tool requires both values to pull accurate data, so don't query them separately.
Can I filter document results using specific criteria with `search_documents`? +
Yep. You can specify filters beyond just keywords. Try adding parameters for Document Type (e.g., 'Notice') or Agency ID to narrow down your search.
What happens if my API key is invalid when running any tool? +
The server will immediately reject the request with an authentication error code. You need to verify and properly pass your active Regulations.gov API Key before making any calls.
How can I filter documents by a specific government agency? +
Use the search_documents tool and provide the agencyId parameter (e.g., 'EPA', 'FAA', or 'CMS'). This will restrict the results to materials published only by that specific agency.
Is it possible to see what the public is saying about a specific rule? +
Yes! Use the search_comments tool with the commentOnId parameter set to the unique Document ID. You can then use get_comment with a specific Comment ID to read the full text of any submission.
How do I get the complete history of a specific rulemaking folder? +
Use the get_docket tool with the specific Docket ID. This retrieves the primary metadata for the docket, while search_documents with the same docket ID can list all associated rules and supporting materials.
We've already built the connector for Regulations.gov. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 6 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.