Warframe

What the Warframe MCP server does

The Warframe MCP server exposes WarframeStat data through four MCP tools. world_state returns a consolidated view of several live activities: the Cetus day/night cycle, Cambion Drift’s Fass/Vome state, Orb Vallis warm/cold conditions, the daily Sortie, Baro Ki’Teer’s status, and the number of active Void Fissures.

get_fissures lists current Void Fissure missions across Lith, Meso, Neo, and Axi relic tiers. Results include the node, mission type, opposing enemy, and remaining time. Steel Path and Void Storm variants are included when active. get_invasions reports unfinished faction Invasions with their node, description, attacking and defending factions, and completion percentage.

The search_items tool performs a fuzzy name search across Warframe data, including warframes, weapons, mods, and other item types. Its results provide the item name, type, category, and description.

How it works

A Warframe MCP server connection can use the Pipeworx gateway endpoint at https://gateway.pipeworx.io/warframe/mcp. The scoped endpoint lists the four Warframe tools along with shared Pipeworx meta-tools. Those shared tools can route broader questions through ask_pipeworx, and the gateway’s initialization response defines the exact tool scope available at connection time.

The same gateway also offers a full endpoint at https://gateway.pipeworx.io/mcp. The difference is which tools are listed directly: the full endpoint exposes the wider catalog, while the Warframe endpoint lists this pack’s tools directly. Both can reach the gateway’s broader data sources through its routing features.

For direct HTTP use, the gateway provides tool endpoints under https://gateway.pipeworx.io/v1/tools/. A POST request to the world_state path can invoke that tool with a JSON body, such as a platform value. Individual tool definitions can be inspected with a GET request.

Setup and configuration

Add the gateway URL to an MCP client’s server configuration:

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

The README names Claude Desktop, Cursor, and Windsurf as supported client examples.

For a local connection, run the package through npx as a stdio MCP server:

{
  "mcpServers": {
    "warframe": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-warframe"]
    }
  }
}

Running npx -y @pipeworx/mcp-warframe directly starts the local server. This mode exposes only the pack’s four tools and does not add Pipeworx shared meta-tools or gateway routing.

Tools and capabilities

• world_state: Read several current Warframe world-state values in one call.
• get_fissures: Find active relic missions, including Steel Path and Void Storm entries.
• get_invasions: Inspect unfinished faction Invasions and their progress.
• search_items: Find warframes, weapons, mods, and other items by approximate name.
• ask_pipeworx: On the gateway connection, ask broader questions in natural language through the shared routing layer.

Limitations and notes

The live tools depend on current WarframeStat data, so their results describe changing game state rather than a fixed dataset. The local package does not include the gateway’s shared meta-tools. Conversely, a gateway pack connection lists additional shared tools beyond the four Warframe-specific tools, which can increase the schemas presented to an MCP client.