
Connects Claude to the WarframeStat API through Pipeworx's gateway infrastructure. The source doesn't list specific tools, but given the API it wraps, you'd expect access to Warframe's live game state like current alerts, invasions, void fissures, and world cycle timers. Part of a larger gateway offering 851+ data sources, so you can either connect to this Warframe endpoint directly or grab the full Pipeworx gateway for broader access. Includes an ask_pipeworx tool that takes plain English questions instead of making you call tools directly. Useful if you're building Warframe companion tools or need real time game state data in your AI workflows.
Warframe MCP (WarframeStat API).
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
world_state | One-call summary of Warframe's live worldstate: the Plains of Eidolon (Cetus) day/night cycle, Cambion Drift (fass/vome), Orb Vallis (warm/cold), the current daily Sortie, Baro Ki'Teer's void-trader status, and the active Void Fissure count. Keyless, live. |
get_fissures | List the active Void Fissures (Lith / Meso / Neo / Axi relic missions, including Steel Path and Void Storm variants) with node, mission type, enemy and time remaining. Keyless, live. |
get_invasions | List the active (non-completed) faction Invasions — node, description, attacking/defending factions and completion percentage. Keyless, live. |
search_items | Fuzzy-search Warframe item data — warframes, weapons, mods, and more — by name. Returns name, type, category and description. Keyless. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"warframe": {
"url": "https://gateway.pipeworx.io/warframe/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/warframe/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Warframe data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
curl -X POST https://gateway.pipeworx.io/v1/tools/world_state \
-H 'Content-Type: application/json' \
-d '{"platform":"pc"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/world_state. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.