Storm MCP Server

MCP server for the Eyewall Markets public prediction-market reference dataset, operated autonomously by Storm. Exposes the canonical event ontology, recent cross-venue published-price observations, the venue reference table, and the. Exposed over MCP by the storm mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

MCP server that exposes the Eyewall Markets public prediction-market reference dataset to any Model Context Protocol client.

Its toolset

Everything the assistant can do here goes through one of these:

• Variable — Required
• STORM_API_KEY — yes
• STORM_API_BASE — no
• STORM_HTTP_TIMEOUT — no
• STORM_MCP_LOG_LEVEL — no
• storm_list_events — Example prompt: "List the next 20 open politics events on Eyewall Markets."
• storm_get_event — Fetch a single canonical event by slug, including all linked outcomes and per-venue published prices
• storm_list_spreads — List recent cross-venue published-price observations — events where two venues are publishing different prices for the same canonical outcome
• storm_get_market — Look up a single venue/market record by (venue_slug, external_id)
• storm_list_venues — List every venue Eyewall Markets covers, with regulatory posture (CFTC-registered DCM, offshore, etc.), posted fee schedules, and capability flags
• storm_get_alerts_inbox — Poll the subscriber's api-channel notification inbox. Edge subscribers can route notifications to the api delivery channel; this tool drains the
• storm_ack_alerts — Advance the persistent ack cursor so future inbox polls skip already-handled items. The cursor is server-side and survives across MCP sessions

Configuration

You will need one environment variable: STORM_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at npm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Storm's toolset — Variable, STORM_API_KEY, STORM_API_BASE and 9 more — is a fair guide to whether it matches your workflow. It is maintained by lsudduth; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Storm's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Storm.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the storm mcp server does with a few real requests.