Federal Register MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Federal Register MCP Server show me recent executive orders from the last month"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Federal Register MCP Server
A Model Context Protocol (MCP) server that provides AI assistants with access to the Federal Register API. This enables searching and retrieving executive orders, presidential documents, rules, and agency information.
What is MCP?
MCP is a protocol that allows AI assistants like Claude to interact with external tools and data sources. This server exposes Federal Register data as a set of tools that can be called by AI assistants.
Related MCP server: regulatory-intel-mcp
Features
Executive Orders: Search, retrieve, and get full text of executive orders by president, year, date range, or keyword
Presidential Documents: Search memoranda and proclamations
Federal Register Documents: Search and retrieve any document type (rules, proposed rules, notices)
Agency Information: List all federal agencies or get details about specific agencies
Public Inspection: View documents before official publication
Roadmap
Hosted version - Deploy a public instance so users can connect without running locally
Legislation tracking - Integrate Congress.gov API and Open States for federal and state legislation
Enriched metadata - Add categories, correlations between executive orders and legislation, impacted populations, and other analytical data
UI experience - Leverage OpenAI Apps to provide a visual interface for exploring executive and legislative data
Installation
# Clone the repository
git clone https://github.com/yourusername/federal-register-mcp.git
cd federal-register-mcp
# Install dependencies
npm install
# Build TypeScript
npm run buildUsage
This server supports two transport modes:
Mode | Transport | Use Case |
stdio (default) | Standard I/O | Claude Desktop (local) |
http | Streamable HTTP | Claude Code, ChatGPT, remote clients |
Claude Desktop (stdio mode)
Add this to your Claude Desktop configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"federal-register": {
"command": "node",
"args": ["/path/to/federal-register-mcp/dist/server.js"]
}
}
}Claude Code (stdio or HTTP mode)
Option 1: stdio (local)
{
"mcpServers": {
"federal-register": {
"command": "node",
"args": ["/path/to/federal-register-mcp/dist/server.js"]
}
}
}Option 2: HTTP (local or remote)
Start the server in HTTP mode:
npm run start:httpThen configure Claude Code to connect to the HTTP endpoint:
{
"mcpServers": {
"federal-register": {
"url": "http://localhost:3000/mcp"
}
}
}ChatGPT (HTTP mode, requires public URL)
ChatGPT cannot connect to localhost. You need to expose the server publicly:
Option 1: ngrok (for development)
# Terminal 1: Start the server
npm run start:http
# Terminal 2: Create a tunnel
ngrok http 3000Then use the ngrok URL (e.g., https://abc123.ngrok.io/mcp) in ChatGPT.
Option 2: Deploy to a cloud host (for production)
Deploy to any HTTPS-capable host:
Cloudflare Workers
Fly.io
Railway
Vercel
AWS / GCP / Azure
The MCP endpoint will be at https://your-host.com/mcp.
Running Directly
# stdio mode (default) - for Claude Desktop
npm start
# HTTP mode - for Claude Code, ChatGPT
npm run start:http
# HTTP mode with custom port
node dist/server.js --http --port 8080
# Or use environment variable
MCP_PORT=8080 npm run start:httpDevelopment
# Edit files in src/*.ts, then build
npm run build
# Or use watch mode for auto-recompile
npm run devHealth Check (HTTP mode)
When running in HTTP mode, a health endpoint is available:
curl http://localhost:3000/health
# {"status":"ok","mode":"http","sessions":0}Available Tools
Tool | Description |
| Search for executive orders by president, year, date range, or keyword |
| Get a specific executive order by its EO number |
| Fetch the complete full text of an executive order |
| Get executive orders signed in the last 30 days |
| Search all Federal Register documents with flexible filtering |
| Fetch a Federal Register document by its document number |
| Fetch the full plain text content of a document |
| Search for presidential memoranda |
| Search for presidential proclamations |
| Get documents currently on public inspection |
| Get a list of all federal agencies |
| Get detailed information about a specific agency |
Example Queries
Once configured, you can ask Claude questions like:
"What executive orders has Joe Biden signed about climate change?"
"Show me Trump's executive orders from his second term (2025)"
"Get the full text of Executive Order 14067"
"What documents are on public inspection today?"
"Find all proposed rules from the EPA in 2024"
API Reference
This server uses the Federal Register API v1. The API is free and requires no authentication.
Project Structure
federal-register-mcp/
├── src/
│ ├── server.ts # MCP server implementation
│ └── federal-register-api.ts # Federal Register API client
├── dist/ # Compiled JavaScript (generated)
├── tsconfig.json
├── package.json
└── README.mdLicense
MIT License - see LICENSE for details.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Available Tools
12 toolsget_agenciesA
Get a list of all federal agencies in the Federal Register system. Returns name, slug, and description for each agency.
Inputs: no named parameters.
get_agencyA
Get detailed information about a specific federal agency including description, URL, and recent document counts.
Inputs: slug (required).
get_documentA
Fetch a Federal Register document by its document number. Works for any document type (rules, notices, presidential documents). Document numbers are formatted as YYYY-NNNNN.
Inputs: document_number (required), fields.
get_document_textA
Fetch the full plain text content of a Federal Register document. First use get_document to get the raw_text_url, then pass it here.
Inputs: raw_text_url (required).
get_executive_orderA
Get a specific executive order by its EO number (e.g., 14067). Returns detailed information including title, abstract, signing date, and links to full text.
Inputs: eo_number (required).
get_executive_order_full_textA
Fetch the complete full text of a specific executive order by its EO number. The full text provides detailed policy language, specific directives, legal citations, and implementation details that are not available in abstracts or titles.
Inputs: eo_number (required).
get_public_inspection_documentsA
Get documents currently on public inspection (available before official publication in the Federal Register). Useful for seeing what will be published tomorrow.
Inputs: no named parameters.
get_recent_executive_ordersA
Get executive orders signed in the last 30 days. Useful for monitoring recent executive actions.
Inputs: no named parameters.
search_documentsA
Search all Federal Register documents with flexible filtering. Use for rules, proposed rules, notices, or presidential documents. Supports full-text search, date ranges, and filtering by agency or president.
Inputs: page, term, type, agency, +6 more.
search_executive_ordersA
Search for executive orders by president, year, date range, or keyword. Returns a list of matching executive orders with metadata including title, signing date, and document links.
Inputs: page, term, year, per_page, +3 more.
search_presidential_memorandaB
Search for presidential memoranda by president, year, or keyword. Memoranda are similar to executive orders but typically used for less formal directives.
Inputs: page, term, year, per_page, +1 more.
search_proclamationsA
Search for presidential proclamations by president, year, or keyword. Proclamations are formal announcements often used for holidays, awareness months, or trade actions.
Inputs: page, term, year, per_page, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Most tools are clearly distinct, with generic document operations and specialized executive order operations separated by use case. However, get_document vs get_executive_order and get_document_text vs get_executive_order_full_text could confuse agents, as both pairs retrieve the same kind of content but require different identifiers.
Tool names consistently follow a verb_noun pattern (get_ or search_), which is predictable and readable. Minor inconsistencies exist: get_document_text uses 'text' while get_executive_order_full_text uses 'full_text', and get_recent_executive_orders places an adjective before the resource, but these deviations are not disruptive.
With 12 tools, the server is well-scoped for its purpose. Each tool serves a clear function in document retrieval, search, presidential document exploration, public inspection, or agency information, without unnecessary redundancy.
The server covers core workflows: searching, fetching metadata, and retrieving full text for any document type. Specialized search tools exist for executive orders, proclamations, and memoranda, but proclamations and memoranda lack dedicated full-text retrieval, requiring agents to use the generic get_document and get_document_text path. This is a minor gap but not a dead end.
Maintenance
Related MCP Connectors
US Federal Register for AI agents: rules, notices, executive orders, agency lookup. No keys.
US Federal Register for AI agents: rules, notices, executive orders, agency lookup. No keys.
Search and trace US federal rules across the Federal Register, eCFR, and Regulations.gov.
Live US federal and state regulatory changes and grant programs for AI agents, with a citation to the official register on every result. Free tier, no account required.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying the US Federal Register API for federal register documents and data through natural language.167 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to search and track US federal regulations, documents, and executive orders from the Federal Register, with no API keys required.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access US FDA regulations (21 CFR) through natural language queries, providing tools for retrieving regulatory information.90 npmMIT
- AlicenseAqualityCmaintenanceEnables AI assistants to retrieve, search, and track changes to US Code of Federal Regulations sections via the eCFR API, returning actual regulation text with citations and point-in-time date support.782 PyPI1MIT