Federal Register MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | The port to run the HTTP server on when using HTTP mode | 3000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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. |
| 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. |
| get_recent_executive_ordersA | Get executive orders signed in the last 30 days. Useful for monitoring recent executive actions. |
| 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. |
| 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. |
| 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. |
| 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. |
| search_proclamationsA | Search for presidential proclamations by president, year, or keyword. Proclamations are formal announcements often used for holidays, awareness months, or trade actions. |
| 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. |
| get_agenciesA | Get a list of all federal agencies in the Federal Register system. Returns name, slug, and description for each agency. |
| get_agencyA | Get detailed information about a specific federal agency including description, URL, and recent document counts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.