Warframe MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Warframe MCP Server search for Sancti Magistar orders"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Warframe MCP Server
Warning: This project was 100% vibecoded and exists purely for my personal needs. Use at your own risk.
A Model Context Protocol (MCP) server that gives AI assistants real-time access to Warframe data. The production Cloudflare Worker exposes read-only Warframe Market search, current orders, closed-order statistics, and a local liquidity estimate, including OpenAI-compatible search and fetch tools. The legacy Node entrypoint retains 19 broader game-data tools.
Cloudflare Worker Tools
Tool | Description |
| Search tradable items by Russian name, English name, or slug |
| Get up to five current sell and buy orders for an item slug |
| Get normalized 48-hour and 90-day closed-order statistics per exact item variant |
| Estimate per-variant liquidity from current orders and 90-day reported volume |
| Return up to ten OpenAI-compatible citation results with stable |
| Resolve a stable item ID to a current market document with top sell and buy orders |
The wfm_* tools return short text plus structuredContent and the applied market filters. Search and top-orders results use retrieved_at; statistics and liquidity results use retrievedAt. The standard search and fetch tools return the OpenAI compatibility shape in structuredContent and duplicate the same object as JSON in text content.
Historical data comes from the deprecated and unsupported Warframe Market v1 statistics route. It is optional: liquidity still reports the current order snapshot when history is unavailable, but returns score=null, grade=unknown, and low confidence. reportedClosedVolume is Warframe Market's reported volume, not a complete or independently verified record of in-game trades.
Related MCP server: SteamDT MCP Server
Legacy Node Tools
Tool | Description |
| Current sortie, archon hunt, nightwave, invasions, open world cycles, events, Steel Path, construction progress, daily deals |
| Baro Ki'Teer status, inventory, and plat-per-ducat value analysis |
| Void Fissure listings with tier/Steel Path/Void Storm/mission type filters |
| Warframe stats, abilities, component drops, build cost, vault status |
| Weapon damage per fire mode, crit/status, components, build info |
| Mod stats at all ranks, polarity, drain, rarity, drop locations |
| Generic item lookup (arcanes, resources, blueprints, companions) |
| Live warframe.market prices — sell/buy stats, cheapest sellers, trade chat messages |
| Drop table search — relics, missions, enemies, with drop chances |
| Which relics contain a prime part, refinement chances, relic farm locations |
| Vaulted / farmable / Varzia resurgence status for prime items |
| Today's Cephalon Simaris synthesis target and scan locations |
| Where specific enemies spawn — confirmed locations from drop tables |
| Top community mod builds from Overframe.gg with mod lists and stats |
| Full crafting recipes — components, credits, build time, sub-recipes |
| Reverse ingredient lookup — "what uses this?" / "safe to sell?" |
| Best nodes to farm multiple resources — dark sector bonuses, overlap scoring |
| Cross-reference Nightwave with fissures/invasions/sortie for max efficiency |
| Find closest in-game color palette match for any hex color (Fashion Frame) |
Most lookup tools accept arrays (batch mode) to handle multiple items in a single call.
Quick Start
npm
git clone https://github.com/YOUR_USER/warframe-mcp.git
cd warframe-mcp
npm install
npm run buildCloudflare Worker (target production runtime):
npm run dev
# Health: http://127.0.0.1:8787/healthz
# MCP: http://127.0.0.1:8787/mcpStdio mode (for MCP clients like Claude Desktop, OpenCode, Cursor):
npm startLegacy Node HTTP mode (Streamable HTTP transport for remote/web clients):
npm run start:http
# Listening on http://127.0.0.1:3000/mcpDocker
docker build -t warframe-mcp .
# HTTP mode (default)
docker run -p 3000:3000 warframe-mcp
# Stdio mode
docker run -i warframe-mcp node dist/index.jsConfiguration
The Cloudflare Worker requires no environment variables. Market tool arguments default to language=ru, platform=pc, and crossplay=true.
The Worker also requires no secrets, KV namespaces, D1 databases, Durable Objects, or service bindings. Its own source uses Worker Web APIs; nodejs_compat remains enabled because the official Cloudflare agents dependency imports Node compatibility modules and the bundle does not build without the flag.
The environment variables below apply only to the legacy Node HTTP entrypoint. None are required.
Variable | Default | Description |
|
| HTTP listen port |
|
| Bind address. Use |
| — | Comma-separated hostnames/IPs allowed through DNS rebinding protection (only needed when |
|
| Idle timeout for legacy HTTP MCP sessions. Sessions older than this are closed and removed by a periodic sweep. Applies only to the legacy Node HTTP server; the Worker |
Example — LAN-accessible server:
HOST=0.0.0.0 PORT=3000 ALLOWED_HOSTS=192.168.1.100,mypc.local npm run start:httpPlatform identifiers
Legacy tools accept the same canonical platform value regardless of the upstream they query. The MCP server normalizes the value internally, so callers never need to know that WarframeStatus uses xb1/swi while Warframe Market uses xbox/switch.
User value | Warframe Market | WarframeStatus |
|
|
|
|
|
|
|
|
|
|
|
|
|
| not supported |
The following legacy aliases are accepted for backward compatibility and map to the canonical value:
Alias | Canonical |
|
|
|
|
|
|
|
|
mobile is only accepted by tools whose upstream exposes it (Warframe Market). Worldstate tools reject mobile with an error listing the accepted values. Unknown values are rejected by all tools; the error message enumerates the accepted canonical values and aliases.
Cloudflare Deployment
Check the bundle without publishing:
npm run deploy:dryFor the first deployment, authenticate Wrangler and publish:
npx wrangler login
npx wrangler whoami
npm run deployWrangler prints the exact deployment URL. With the configured Worker name and a standard workers.dev subdomain, the endpoints have this form:
Health: https://warframe-mcp.<YOUR_WORKERS_SUBDOMAIN>.workers.dev/healthz
MCP: https://warframe-mcp.<YOUR_WORKERS_SUBDOMAIN>.workers.dev/mcpReplace the placeholder with the subdomain shown by Wrangler. A configured Cloudflare custom domain can be used instead.
Client Setup
ChatGPT
ChatGPT requires a reachable HTTPS remote MCP endpoint; it cannot connect directly to localhost. The current setup flow is documented in ChatGPT Developer mode:
In ChatGPT on the web, enable Developer mode under Settings → Security and login.
Open Settings → Plugins, select the plus button, and create a developer-mode app.
Set the server URL to
https://warframe-mcp.<YOUR_WORKERS_SUBDOMAIN>.workers.dev/mcp.Select No Authentication. The pilot exposes only public read-only data.
Refresh or scan the tools and confirm that
wfm_search_items,wfm_get_top_orders,wfm_get_item_statistics,wfm_get_item_liquidity,search, andfetchare visible.In a conversation, select Developer mode and enable the created app.
Use the ready-to-paste project guidance from docs/chatgpt-project-instructions.md so price questions always use current MCP data.
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"warframe": {
"command": "node",
"args": ["/absolute/path/to/warframe-mcp/dist/index.js"]
}
}
}Claude Desktop (Docker)
{
"mcpServers": {
"warframe": {
"command": "docker",
"args": ["run", "-i", "--rm", "warframe-mcp", "node", "dist/index.js"]
}
}
}OpenCode
Add to opencode.json:
{
"mcpServers": {
"warframe": {
"command": "node",
"args": ["/absolute/path/to/warframe-mcp/dist/index.js"]
}
}
}Cloudflare Worker clients (Streamable HTTP)
Run the Worker locally, then connect to http://127.0.0.1:8787/mcp:
npm run dev
# GET /healthz — service health
# POST /mcp — stateless MCP JSON-RPC requestsThe Worker creates a fresh MCP server and transport for every request. It does not store HTTP sessions and requires no authentication.
Warframe Market access is coordinated per Worker isolate: at most three external requests start per second, transient failures are retried with Retry-After or bounded jittered backoff, and identical concurrent requests are deduplicated. The item catalog is cached for six hours, current full/top order snapshots for 20 seconds, and legacy statistics for five minutes.
Typical flow:
Call
searchwith{"query":"Титания Прайм"}.Pass the returned
wfm:item:<slug>ID tofetch.
The direct market flow remains available through wfm_search_items followed by wfm_get_top_orders, wfm_get_item_statistics, or wfm_get_item_liquidity. Pass the exact rank, subtype, charges, amberStars, or cyanStars when the item has variants.
Legacy Node HTTP clients
Start the server in HTTP mode, then connect to http://localhost:3000/mcp:
npm run start:http
# POST /mcp — JSON-RPC requests (initialize, tools/list, tools/call)
# GET /mcp — SSE stream for server-to-client notifications
# DELETE /mcp — Session terminationSessions are managed via the Mcp-Session-Id header. Send an initialize request without a session ID to start a new session.
Smoke Test
For the production Worker surface, start Wrangler and connect an MCP client to http://127.0.0.1:8787/mcp:
npm run devComplete MCP initialize, then verify tools/list contains all six Worker tools. Exercise:
wfm_get_item_statistics {"slug":"arcane_energize","rank":0}
wfm_get_item_statistics {"slug":"arcane_energize","rank":5}
wfm_get_item_liquidity {"slug":"arcane_energize","rank":0}
wfm_get_item_liquidity {"slug":"arcane_energize","rank":5}Confirm the ranks remain separate. Also check one non-ranked Prime component, one ranked mod, and one current catalog item with subtypes; subtype availability can change with the upstream catalog. Review warnings and timestamps in every statistics/liquidity result. These smoke calls use the public API; automated tests use only mocks and fixtures.
For the legacy Node entrypoint:
# Stdio — should return JSON with 19 tools
echo '{"jsonrpc":"2.0","method":"tools/list","id":1}' | node dist/index.js
# HTTP — initialize a session
curl -X POST http://localhost:3000/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"test","version":"0.1"}},"id":1}'System Prompt
SYSTEM_PROMPT.md contains a ready-to-use system prompt for an AI assistant that uses this MCP server. It includes tool documentation, a decision tree for tool selection, multi-tool chaining strategies, batching guidance, and Warframe domain knowledge (relics, rotations, trading, modding, Steel Path, open world cycles).
Architecture
worker/
├── index.ts # Cloudflare Worker: /healthz + stateless /mcp tools
├── market-analytics.ts # Pure statistics normalization and liquidity heuristic
├── openai-compat.ts # Stable document IDs and OpenAI search/fetch documents
└── warframe-market.ts # Worker-safe Market API client, reliability, and caches
wrangler.jsonc # Worker entrypoint and compatibility settings
tsconfig.worker.json # Worker-only TypeScript configuration
vitest.config.ts # Tests executed in the Workers runtime
src/
├── index.ts # Entry point — stdio or HTTP transport
├── api/
│ ├── warframestat.ts # warframestat.us client (items, drops, worldstate)
│ ├── warframe-market.ts # warframe.market v2 client (prices, orders)
│ ├── overframe.ts # Overframe.gg scraper (community builds)
│ └── wiki.ts # Fandom wiki API client (crafting recipes)
├── tools/
│ ├── worldstate.ts # world_state, baro_kiteer, active_fissures
│ ├── items.ts # lookup_warframe, lookup_weapon, lookup_mod, lookup_item
│ ├── market.ts # market_price_check
│ ├── drops.ts # search_drops, relic_drops
│ ├── primeVault.ts # prime_vault_status
│ ├── simaris.ts # simaris_target
│ ├── enemy.ts # find_enemy_spawn
│ ├── builds.ts # lookup_builds
│ ├── crafting.ts # crafting_requirements, crafting_usage
│ ├── farmOptimizer.ts # farm_route_optimizer
│ ├── synergy.ts # task_synergy_planner
│ └── colors.ts # color_palette_finder
├── types/
│ ├── warframestat.ts # warframestat.us API types
│ ├── warframe-market.ts # warframe.market v2 types
│ ├── overframe.ts # Overframe build types
│ └── index.ts # Re-exports
├── data/
│ ├── color-palettes.ts # 31 Warframe color palettes (2,790 colors)
│ └── planet-resources.ts # Planet resource drops, dark sector nodes & bonuses
└── utils/
├── cache.ts # TTL cache (60s–24h depending on data type)
├── formatting.ts # Number/time formatting helpers
└── lua-parser.ts # Lua table parser for wiki blueprint dataData Sources
API | Base URL | Auth | Used For |
| None | World state, items, drops, mods, weapons, warframes | |
| None | Tradable item catalog and current full/top orders | |
warframe.market legacy statistics |
| None | Deprecated 48-hour and 90-day closed-order statistics; optional and allowed to degrade |
| None (HTML scraping) | Community mod builds | |
MediaWiki API | None | Crafting recipes (blueprint data) | |
Bundled static data | — | — | Planet resources, dark sector bonuses, 31 color palettes (2,790 colors) |
Caching
Data Type | TTL | Examples |
World state | 60 seconds | Fissures, invasions, cycles |
Drop tables | 5 minutes | Drop search results |
Worker market items | 6 hours | Item listing catalog |
Worker full orders | 20 seconds | Current visible order book used for counts and best-price depth |
Worker top orders | 20 seconds | Current buy/sell snapshot |
Worker legacy statistics | 5 minutes | Closed-order 48-hour and 90-day buckets |
Static data | 24 hours | Warframe/weapon/mod stats |
Wiki data | 24 hours | Crafting recipes |
Overframe builds | 6 hours | Community builds |
Pilot Limitations
The production Worker exposes only
wfm_search_items,wfm_get_top_orders,wfm_get_item_statistics,wfm_get_item_liquidity,search, andfetch.It is read-only: there is no Warframe Market login, private profile access, or order mutation.
Prices and order counts are current snapshots, not guarantees of an executable trade. Historical volume is reported by a deprecated upstream route and the liquidity score is a deterministic local heuristic, not a profit or execution prediction.
Cache, request limiting, and request deduplication are isolate-local and reset on a cold start.
The public endpoint has no application authentication or per-user authorization.
Availability depends on Cloudflare Workers and the public Warframe Market API; the pilot has no SLA.
ChatGPT developer-mode availability and workspace permissions depend on the current ChatGPT plan and admin policy.
Development
npm run dev # Run the Cloudflare Worker locally
npm run dev:stdio # Watch-compile the legacy Node entrypoint
npm run typecheck # Type-check without emitting dist
npm test # Build and run automated tests
npm run build # One-shot compile
npm run deploy:dry # Build the Worker deployment bundle without uploading
npm run deploy # Publish through the authenticated Wrangler account
npm run check # Type-check, test, and dry-run the Worker bundle
npm start # Run stdio modeRequirements
Node.js >= 20.3 (required by Wrangler)
TypeScript 5.x
Worker runtime dependencies:
@modelcontextprotocol/sdk,agents, andzodExpress is used only by the legacy Node HTTP entrypoint and is not bundled into the Worker
License
MIT
Available Tools
19 toolsactive_fissuresB
List active Void Fissure missions, filterable by tier, Steel Path, Void Storm, and mission type.
Inputs: tier, platform, steel_path, void_storm, +1 more.
baro_kiteerA
Check Baro Ki'Teer's current status, inventory, and optional plat-per-ducat worth analysis.
Inputs: platform, show_worth_analysis.
color_palette_finderA
Find the closest matching color in Warframe's color palettes. Input a hex color code and get the exact palette, row, and column of the best match. Fashion Frame endgame tool.
Inputs: hex_color (required), limit, palette.
crafting_requirementsA
Look up the full crafting recipe for one or more Warframe items — components, credits, build time, and sub-recipes. Answers 'what do I need to build X?'
Inputs: item_names (required).
crafting_usageA
Find all items that use one or more given resources or components as crafting ingredients. Answers 'what is this used for?' and 'is it safe to sell?'
Inputs: item_names (required).
farm_route_optimizerA
Find the best mission nodes to farm multiple resources simultaneously. Cross-references planet drop tables and dark sector bonuses to find overlapping farm spots.
Inputs: resources (required), prefer_mission_type.
find_enemy_spawnA
Find where one or more specific enemies spawn: confirmed locations from drop tables and likely faction nodes.
Inputs: enemies (required), steel_path, mission_preference.
lookup_buildsA
Find popular community mod builds for one or more Warframes, weapons, or companions from Overframe.gg. Returns top-voted builds with mod lists, computed stats, and build guides.
Inputs: item_names (required), limit, category.
lookup_itemB
Look up one or more items (arcanes, resources, blueprints, etc.) by name with dynamic formatting of available fields.
Inputs: names (required).
lookup_modA
Look up one or more mods by name: stats progression, polarity, drain, rarity, and drop locations.
Inputs: names (required).
lookup_warframeA
Look up one or more Warframes by name: stats, abilities, component drop sources, build requirements, and vault status.
Inputs: names (required).
lookup_weaponA
Look up one or more weapons by name: damage stats per fire mode, crit/status, components, and build info.
Inputs: names (required).
market_price_checkA
Check live trading prices for one or more tradeable items on warframe.market: sell/buy stats, cheapest sellers, and trade chat messages.
Inputs: item_names (required), mod_rank, platform, online_only.
prime_vault_statusA
Check if one or more Prime items are vaulted, available from Varzia (Prime Resurgence), or currently farmable from relics.
Inputs: names (required).
relic_dropsA
Find which relics contain one or more specific prime parts, with refinement chances and optional relic farming locations.
Inputs: queries (required), show_relic_sources.
search_dropsA
Search drop tables for one or more items: shows where they drop, from which relics, missions, and enemies, with drop chances.
Inputs: queries (required), limit, min_chance.
simaris_targetA
Check today's Cephalon Simaris synthesis target and recommended scanning locations.
Inputs: platform.
task_synergy_plannerA
Find the most efficient activity combos by cross-referencing active Nightwave challenges with current Fissures, Invasions, and Sortie. Tells you which single mission can complete multiple objectives at once.
Inputs: platform.
world_stateA
Get current Warframe world state: sortie, archon hunt, nightwave, invasions, open world cycles, events, steel path, construction progress, and daily deals.
Inputs: platform, sections.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 19 tools
Each tool has a clearly distinct purpose, ranging from world state queries to specific lookups (warframes, weapons, mods, items) and specialized planners (farming, task synergy, color palette). No two tools overlap significantly, minimizing confusion for an agent.
Most tool names follow a verb_noun pattern (e.g., lookup_warframe, search_drops, find_enemy_spawn), but some deviate (e.g., world_state, active_fissures, market_price_check). The mix is readable and predictable, with only minor inconsistencies.
With 19 tools, the server covers the major facets of Warframe: game state, items, trading, crafting, farming, and builds. Each tool serves a clear function, and the count feels well-scoped without being overwhelming or sparse.
The tool set covers core Warframe activities like world state, fissures, item lookups, crafting, trading, and farming. Notable gaps include lack of explicit support for kuva liches/sisters of parvos or clan-related features, but the surface is sufficient for most common agent tasks.
Maintenance
Related MCP Connectors
Live crypto + IDX stock market intelligence for AI agents — 19 tools, no API key.
Live TCG card and decklist prices for AI assistants. 22+ games, no account, ready-to-buy links.
Pay-per-use tool marketplace for AI agents. Search, price-check, and call APIs via MCP.
Pre-computed market data that improves agent reasoning, reduces token usage, and replaces pipelines.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables querying Steam item prices, wear, and price history via the SteamDT API, allowing AI assistants to retrieve and analyze Steam marketplace data.13-
- AlicenseAqualityDmaintenanceEnables AI assistants to query CS2 item real-time prices, K-line data, market index, wear, and inspect images via the SteamDT API.132MIT
- AlicenseNot gradedqualityDmaintenanceEnables searching Warframe items, viewing price history, and managing buy/sell orders through the Warframe Market API.15 npm1GPL 3.0
- AlicenseAqualityDmaintenanceProvides AI assistants with real-time access to Warframe game data including world state, item stats, market prices, drop tables, builds, crafting, and farming optimization through 19 tools.121966 npm1MIT