Integration

Regulations.gov integration

Regulations.gov is the US federal rulemaking portal. Search the documents agencies post (proposed rules, final rules, notices, supporting material) by keyword, agency, docket, type, posting date or open comment period, read one document with its comment window, Federal Register number and downloadable files, search and read the public comments filed on a document, and search and read dockets (the folder grouping a rulemaking's documents). Posting a comment, and the submission-key and file-upload routes that serve it, are not exposed: commenting needs a separately approved key. Authentication is an api.data.gov key sent in the X-Api-Key header.

Connect Regulations.gov How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Regulations.gov.Built from the 7 Regulations.gov tools below, on the connection you add once.

What you can do with Regulations.gov

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Comment, 2 operations

get_commentGet commentGETReturns one public comment: its text, the document it comments on, docket, agency, dates, tracking number and file links, plus submitter fields the agency chose to publish. Pass include=attachments to also get its attachments.
list_commentsList commentsGETSearches public comments by keyword, agency, posting or modification date, or the document commented on. A query returns at most 20 pages; for more, sort by lastModifiedDate and move a filter[lastModifiedDate][ge] window forward.

Docket, 2 operations

get_docketGet docketGETReturns one docket's record: title, abstract, type, agency, Regulation Identifier Number (RIN), keywords, program and modification date.
list_docketsList docketsGETSearches dockets (the folder grouping a rulemaking's or other action's documents) by keyword, agency, docket type or last modification time. Each result carries the docketId, title and type.

Document, 2 operations

get_documentGet documentGETReturns one document's full record: title, type, agency, docket, comment period, Federal Register citation, abstract and file download links. Pass include=attachments to also get its attachments.
list_documentsList documentsGETSearches documents posted on Regulations.gov (proposed rules, rules, notices, supporting material) by keyword, agency, docket, type, dates or open comment period. Each result carries its documentId and objectId, title, type and comment dates.

Agency category, 1 operation

list_agency_categoriesList agency categoriesGETLists the commenter categories an agency uses to group the comments it receives (for example Academia or Animal Feed Industry), the values a comment's category attribute can take.

Use Regulations.gov from Claude Code, Cursor or Codex

Connect Regulations.gov in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Regulations.gov operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Regulations.gov

Create your workspace
Sign up free. Nothing to install.
Connect Regulations.gov once
Add your Regulations.gov connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.