Fred St Louis MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRED_API_KEY | Yes | A FRED API key from FRED API Keys (https://fred.stlouisfed.org/docs/api/api_key.html) |
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 |
|---|---|
| fred_requestC | Call any FRED API v1 endpoint path directly. |
| geofred_requestC | Call any GeoFRED API endpoint path directly. |
| fred_v2_requestB | Call any FRED API v2 endpoint path directly. |
| get_categoryD | fred/category |
| get_category_childrenD | fred/category/children |
| get_category_relatedD | fred/category/related |
| get_category_seriesD | fred/category/series |
| get_category_tagsD | fred/category/tags |
| get_category_related_tagsD | fred/category/related_tags |
| get_releasesD | fred/releases |
| get_releases_datesD | fred/releases/dates |
| get_releaseD | fred/release |
| get_release_datesD | fred/release/dates |
| get_release_seriesD | fred/release/series |
| get_release_sourcesD | fred/release/sources |
| get_release_tagsD | fred/release/tags |
| get_release_related_tagsD | fred/release/related_tags |
| get_release_tablesD | fred/release/tables |
| get_seriesD | fred/series |
| get_series_categoriesD | fred/series/categories |
| get_observationsD | fred/series/observations |
| get_series_observationsD | Alias for get_observations. |
| get_series_releaseD | fred/series/release |
| search_seriesD | fred/series/search |
| search_series_by_tagsD | fred/series/search/tags |
| search_series_related_tagsD | fred/series/search/related_tags |
| get_series_tagsD | fred/series/tags |
| get_series_updatesD | fred/series/updates |
| get_series_vintage_datesD | fred/series/vintagedates |
| get_sourcesD | fred/sources |
| get_sourceD | fred/source |
| get_source_releasesD | fred/source/releases |
| get_tagsD | fred/tags |
| get_related_tagsD | fred/related_tags |
| get_tag_seriesD | fred/tags/series |
| get_map_shape_fileD | geofred/shapes/file |
| get_map_series_groupD | geofred/series/group |
| get_map_series_dataD | geofred/series/data |
| get_map_regional_dataD | geofred/regional/data |
| get_release_observations_v2D | fred/v2/release/observations |
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 40 tools
Most tools have distinct purposes targeting specific FRED resources and operations, but there is some overlap between general request tools (fred_request, fred_v2_request, geofred_request) and specific endpoint tools, which could cause confusion about when to use which. The alias 'get_series_observations' duplicates 'get_observations', adding minor redundancy.
Tool names follow a highly consistent verb_noun pattern (e.g., get_category, search_series, get_release_dates) with clear snake_case throughout. The three general request tools (fred_request, fred_v2_request, geofred_request) deviate slightly but maintain a predictable naming style.
With 40 tools, the count is excessive for the FRED API domain, making the surface overwhelming and likely to confuse agents. A more focused set of 10-20 tools covering core operations would be more appropriate, as many tools are highly specific (e.g., get_category_related_tags, get_release_tables) that could be consolidated.
The tool set provides comprehensive coverage of the FRED API domain, including categories, series, releases, sources, tags, and geospatial data, with full CRUD-like operations (mostly GET/search) and no apparent gaps. It supports all major workflows for economic data retrieval and analysis.