FRED MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | HTTP bind address. Default: all interfaces. | |
| PORT | No | HTTP port. Default: 3000. | |
| LOG_LEVEL | No | Log level: error, warn, info, or debug; logs go to stderr. Default: info. | |
| TRANSPORT | No | Set to 'http' for Streamable HTTP transport. Default: stdio. | |
| FRED_API_KEY | Yes | Your FRED API key (required). Obtain one from https://fred.stlouisfed.org/docs/api/api_key.html. | |
| MCP_BODY_LIMIT | No | Maximum accepted JSON body size. Default: 1mb. | |
| MCP_MAX_SESSIONS | No | Maximum concurrent MCP sessions; new sessions get 503 beyond this. Default: 100. | |
| FRED_CACHE_TTL_MS | No | TTL for cached API responses; 0 disables caching. Default: 60000. | |
| MCP_SESSION_TTL_MS | No | Idle time before a session is reaped. Default: 1800000. | |
| FRED_API_TIMEOUT_MS | No | Per-request timeout against the FRED API. Default: 30000. | |
| FRED_API_MAX_RETRIES | No | Retries for 429/5xx/network failures with exponential backoff and jitter. Default: 3. | |
| FRED_CACHE_MAX_ENTRIES | No | LRU cache capacity. Default: 500. | |
| FRED_RATE_LIMIT_PER_MINUTE | No | Client-side token bucket matching FRED's per-key quota. Default: 120. | |
| FRED_API_RETRY_BASE_DELAY_MS | No | Base delay for retry backoff. Default: 500. | |
| MCP_SESSION_SWEEP_INTERVAL_MS | No | How often the idle-session reaper runs. Default: 60000. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityActive
ResponsivenessNo issues