global-macro-forecast-mcp
v0.3.1
Published
Read-only stdio MCP server for published overseas macro market forecast probability data
Readme
WorkBuddy read-only macro probability MCP
This package exposes a local Node.js stdio MCP server for the approved public Pages snapshot at:
https://sarz-innson.github.io/global-macro-forecast-pages/It is read-only and does not access private GitHub artifacts, Gamma, Polymarket, credentials, or user-supplied URLs.
Requirements and checks
- Node.js 22 or newer
- No runtime configuration variables
Tools
list_events: browse events with optional category, bounded limit, and stable cursor.search_events: search events with a small explicit Chinese/English macro lexicon.get_event_probability: return every option for one event, each latest probability and source timestamp, and compact or full history. Results are chart-ready data only; the WorkBuddy skillmacro-event-probabilityinstructs the agent to draw the probability-history chart natively.
All tools advertise readOnlyHint: true. Not-found results have status: "not_found"; feed errors use explicit status/code JSON instead of pretending a missing probability is zero.
Chart behavior
For a found event, get_event_probability returns the complete structured probability result as text/structured content.
The host renders charts natively: the accompanying skill instructs the agent to draw a probability-history line chart from markets[].history (t/p points), using at most the six highest-probability options, with option names and latest probabilities in the legend, and the snapshot time from data_as_of.
A client without native chart drawing can still use the complete JSON data.
Local stdio launch
Start the server directly for protocol-level testing:
npm start --prefix workbuddy-mcpFor a client configuration, use the absolute path to this machine's Node binary and this repository's absolute src/server.mjs path:
{
"command": "/absolute/path/to/node",
"args": [
"/absolute/path/to/github-global-macro-forecast/workbuddy-mcp/src/server.mjs"
]
}The client must communicate over stdio. The server keeps stdout reserved for MCP JSON-RPC; any diagnostics go to stderr.
