# Regulations.gov MCP > 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. ## Overview - **Category:** document-management - **Price:** Free - **Tags:** federal-regulations, rulemaking, public-policy, compliance, docket-tracking, legislative-data ## Description 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. ## Tools ### 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. ### search_comments Searches and filters public comments based on keywords or date ranges across multiple dockets. ### search_dockets Finds general information about rulemaking dockets using search criteria like agency name or topic. ### search_documents Searches for any official document type (rules, notices) across the federal database. ## Prompt Examples **Prompt:** ``` Search for recent documents from the EPA related to 'air quality' posted after 2024-01-01. ``` **Response:** ``` I've found several documents from the EPA regarding air quality. The most recent is a Proposed Rule (ID: EPA-HQ-OAR-2023-0014) regarding emission standards. Would you like to see the full details or the associated comments? ``` **Prompt:** ``` Find public comments submitted for document ID FAA-2023-1234-0001. ``` **Response:** ``` I've retrieved 15 public comments for that FAA document. They range from industry feedback to individual pilot concerns. I can summarize the top comments or fetch the full text of a specific one for you. ``` **Prompt:** ``` Get the full details for docket folder CMS-2024-0005. ``` **Response:** ``` Accessing docket CMS-2024-0005... This docket is managed by the Centers for Medicare & Medicaid Services and contains 3 supporting documents and 1 final rule. The last modification was on 2024-02-15. ``` ## Capabilities ### Search Documents Find rules, notices, and proposed regulations by keywords, date, or agency ID. ### Track Dockets Get complete details for a specific rulemaking docket folder. ### Search Public Comments Find and analyze public feedback submitted to federal agencies based on criteria. ### Retrieve Specific Documents Pull the full details for one document ID you already know about. ### Get Comment Details Fetch all specific information associated with a single public comment. ## Use Cases ### 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. ## Benefits - **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. ## How It 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. 1. Subscribe to this server and enter your Regulations.gov API Key. 2. Your AI client (Claude, Cursor, etc.) sends a query using the specific tool function you need (e.g., `search_documents`). 3. The server runs the request against the federal database and returns structured data—like comment text or docket details—to your agent. ## Frequently Asked Questions **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.