fcc-ecfs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ECFS_API_KEY | Yes | Your FCC ECFS API key. Required to access the FCC's Electronic Comment Filing System public API. |
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 |
|---|---|
| ecfs_search_filingsB | Search filings submitted to the FCC's Electronic Comment Filing System (ECFS). Filter by proceeding/docket number, filer name, submission type, and date received. |
| ecfs_get_filingB | Fetch a single ECFS filing by its submission ID. |
| ecfs_search_proceedingsC | Search proceedings (dockets) registered in the FCC ECFS system, e.g. by docket number. |
| ecfs_get_download_planA | Get a download plan for a filings search — the same filters as ecfs_search_filings, but instead of a page of results, returns date_submission-range buckets each with a suggested_api_call safe to run to exhaustively page a large docket. Use this before ecfs_search_filings for dockets with thousands of filings (e.g. a heavily-commented NPRM): plain offset/limit paging over a large result set can return duplicate or missing filings, which the download plan's date-bucketed queries avoid. |
| ecfs_search_documentsA | List the documents (attachments) associated with one or more ECFS filings, by submission ID. Returns document metadata (filename, page count, byte size, OCR status, and its viewer location) — not the document's file contents. Use ecfs_download_document to save a document's PDF. |
| ecfs_download_documentA | Download one document (usually a PDF) from an ECFS filing and save it to disk, returning the saved file path. Identify it by the filing's submission ID and the document's position in the filing — the {n} in its https://www.fcc.gov/ecfs/document/{id_submission}/{n} location/src URL. Fetches the file through a headless Chrome browser (Google Chrome must be installed), so it takes a few seconds per document. |
| ecfs_list_inboxesA | List the available inboxes for non-docketed filings in ECFS. |
| ecfs_raw_requestA | Escape hatch for calling any ECFS public API path/query parameters not covered by the other tools. The api_key is added automatically; do not include it yourself. |
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 8 tools
Each tool has a clearly distinct purpose: filing lookup, proceeding search, document metadata listing, document download, inbox listing, raw API escape hatch, and a specialized download-plan helper. The potential overlap between ecfs_search_filings and ecfs_get_download_plan is explicitly resolved in the description, and search_documents vs download_document are cleanly separated by metadata vs file retrieval.
All tools share the ecfs_ prefix and snake_case formatting, and nearly all follow a verb_noun pattern (get_filing, search_proceedings, download_document). The main deviation is ecfs_raw_request, which is an adjective_noun phrase rather than a verb_noun action, but it remains readable and stylistically consistent.
Eight tools is well-scoped for the FCC ECFS domain, covering search, retrieval, document handling, and an escape hatch without excessive surface area. Each tool appears to earn its place, and there is no sign of redundant or filler operations.
The core ECFS read workflows are covered: search/get filings, search proceedings, list/get document metadata, download documents, list inboxes, and raw API access. Minor gaps exist, such as a direct proceeding-detail lookup and inbox-specific filing retrieval, but the raw_request tool provides a workaround for uncovered API paths.