ForexFactory MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_TTL | No | Cache time (seconds) for repeated queries | 300 |
| NAMESPACE | No | MCP namespace for tools/resources | ffcal |
| FF_BASE_URL | No | Base URL for scraping | https://www.forexfactory.com/calendar |
| EXCLUDE_FIELDS | No | Control which fields to exclude in normalized event data | |
| INCLUDE_FIELDS | No | Control which fields to include in normalized event data (supports wildcards) | |
| LOCAL_TIMEZONE | No | Local timezone override (uses system local if not set) | |
| SCRAPER_TIMEOUT_MS | No | Timeout for Playwright in milliseconds | 5000 |
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 |
|---|---|
| my-ffcal_get_calendar_eventsC | Retrieve ForexFactory calendar events for a given time period or custom date range.Valid |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| my-ffcal_daily_prep | Summarize today’s economic calendar into a trader prep note. |
| my-ffcal_weekly_outlook | Summarize high-impact economic events for the upcoming week. |
| my-ffcal_daily_playbook | FX daily trading playbook: overnight recap, session handoff, key levels, and today’s risk events with tactical FX setups. |
| my-ffcal_weekly_outlook_next_week | Sunday note: summarize next week’s macro events by theme and currency, with expected volatility windows and cross-asset spillovers. |
| my-ffcal_cross_asset_radar | Cluster week’s events by cross-asset spillovers (oil→CAD, gold→AUD, US yields→USD/JPY). Highlight non-FX drivers relevant to FX. |
| my-ffcal_positioning_flow_note | Summarize CFTC positioning, ETF flows, and key options expiries overlapping macro events; highlight where positioning may amplify volatility. |
| my-ffcal_volatility_grid | Heatmap of weekly event risk: x-axis time zones (Asia/London/NY), y-axis days; bold high-impact; note vol clustering. |
| my-ffcal_trade_map_scenarios | For a chosen event, outline upside/inline/downside scenarios with bias for USD, equities, yields, and concrete FX trade ideas. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| events_today | Economic calendar events scheduled for today. |
| events_week | All economic calendar events scheduled for this week. |
| events_yesterday | Economic calendar events from yesterday. |
| events_next_week | All economic calendar events scheduled for next week. |
| events_tomorrow | Economic calendar events scheduled for tomorrow. |
| events_this_week | All economic calendar events scheduled for this week. |
| events_last_week | All economic calendar events from last week. |
| events_this_month | All economic calendar events scheduled for this month. |
| events_next_month | All economic calendar events scheduled for next month. |
| events_last_month | All economic calendar events from last month. |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose: retrieving ForexFactory calendar events.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'my-ffcal_get_calendar_events' follows a verb_noun pattern, which is consistent with itself.
A single tool is generally too few for a server's purpose, as it limits functionality and scope. For a ForexFactory calendar server, one might expect additional tools for filtering, sorting, or managing events, making this count feel thin and under-scoped.
The server only provides retrieval of calendar events, with no tools for creating, updating, deleting, or otherwise managing events. This is a significant gap, as it lacks basic CRUD operations and limits the server's utility to read-only access.