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_filingsC | 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_proceedingsA | 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. |
| 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 7 tools
Each tool targets a distinct action and resource: searching filings, retrieving a filing, searching proceedings, planning exhaustive downloads, listing documents, listing inboxes, or making raw API calls. The only potentially overlapping pair (ecfs_search_filings vs ecfs_get_download_plan) is clearly differentiated by the download plan's explicit purpose of returning date-bucketed query plans rather than results.
All tool names share the consistent 'ecfs_' prefix followed by a clear verb_noun structure: search_filings, get_filing, search_proceedings, get_download_plan, search_documents, list_inboxes, raw_request. The verbs (search/get/list) are standard and applied appropriately to each operation, making the naming pattern predictable and easily parseable.
With exactly 7 tools, the server is compactly scoped to the FCC ECFS public API domain—covering the main search/retrieval workflows without unnecessary bloat. Each tool serves a clear purpose, and the addition of an escape hatch (ecfs_raw_request) keeps the surface lean while ensuring full API coverage.
The tool set covers the core workflows for the domain: searching and retrieving filings, exploring proceedings, managing large result sets with a download plan, listing document metadata, and accessing inboxes. The ecfs_raw_request tool acts as a catch-all for any uncovered API endpoints, so the surface has no obvious dead ends for public read-only ECFS queries.