fred-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRED_API_KEY | Yes | Your free FRED API key from https://fred.stlouisfed.org/docs/api/api_key_request.html | |
| FRED_MCP_CACHE | No | Set to '0' to disable caching (optional) | |
| FRED_MCP_USER_AGENT | No | Custom user agent string to identify your deployment (optional) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_seriesA | Find FRED series by free-text search, best matches first. |
| get_seriesA | Full metadata for one series: units, frequency, range, and notes. |
| get_observationsA | A series' values in a date window, optionally transformed/downsampled. |
| get_latestA | The most recent value of a series, plus its next scheduled release. |
| compare_seriesA | Align 2-5 series on one date axis for comparison. |
| get_release_calendarA | Upcoming data-release dates ("when is the next jobs report / CPI?"). |
| get_series_as_ofA | A series EXACTLY as it was known on a past date — before later revisions. |
| get_revision_historyA | One data point's life across revisions: earliest archived print -> today. |
| get_vintage_datesA | When a series' data was released or revised (its ALFRED vintages). |
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 9 tools
Each tool targets a distinct operation on FRED data: search, metadata, observations, latest value, revision history, vintage dates, as-of data, release calendar, and multiple series comparison. No two tools overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_observations, search_series). No mixing of conventions or ambiguous verbs.
9 tools cover the essential FRED API operations without being excessive. The count is well-scoped for an agent to effectively interact with economic data.
The set covers the full lifecycle: search and discovery, metadata retrieval, raw data access, revision history, vintage snapshots, release dates, and cross-series comparison. No critical operations are missing for typical use cases.