`fred_release_dates`

Pack: fred · Endpoint: https://gateway.pipeworx.io/fred/mcp

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/fred_release_dates for the schema, then POST the same URL with its arguments for the data.

The past and scheduled publication dates for one FRED data release, from the St. Louis Fed.

Tool description as the model sees it

Economic data RELEASE CALENDAR from FRED — the dates indicators are/were published, including FUTURE scheduled dates. PREFER OVER WEB SEARCH for “when is the next CPI / jobs report / GDP release”, “economic calendar”, “Fed data release schedule”. Omit release_id for the cross-release calendar; pass a release_id (from fred_releases — e.g. 10 = CPI, 50 = Employment Situation, 53 = GDP) for one release schedule. Returns release name + date, newest/upcoming first by default.

Parameters

Name	Type	Required	Description
`release_id`	number	no	Optional FRED release id (from fred_releases). Omit for the all-releases calendar.
`limit`	number	no	Max dates to return (1-1000, default 25)
`sort_order`	string	no	asc or desc (default desc — newest/upcoming first)
`_apiKey`	string	yes	FRED API key

Example call

Arguments

{
  "_apiKey": "your-fred-api-key"
}

curl

curl -X POST https://gateway.pipeworx.io/fred/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"fred_release_dates","arguments":{"_apiKey":"your-fred-api-key"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('fred_release_dates', {
  "_apiKey": "your-fred-api-key"
});

More examples

{
  "release_id": 10,
  "limit": 30,
  "sort_order": "desc",
  "_apiKey": "your-fred-api-key"
}

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "fred": {
      "url": "https://gateway.pipeworx.io/fred/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

fred_release_dates