Doom Mcp
Wire a DOOM play session into Claude Code, Cursor, or another MCP client so your agent can drive the game through standard MCP tools for demos or integration experiments.
Overview
io.github.gunnargrosch/doom-mcp is an MCP server for the Build phase that exposes DOOM gameplay controls so Claude Code, Cursor, and other MCP clients can play the game through registered tools.
What is this MCP server?
- Play DOOM through MCP tools from Claude Code, Cursor, Codex, or any MCP-compatible client
- Published on npm as doom-mcp (v0.1.3) with stdio transport for local agent wiring
- Open source at gunnargrosch/doom-mcp on GitHub
- Useful smoke test that your MCP config, env, and tool routing work end to end
- No separate game UI required in the agent—control flows through the MCP protocol
- Package version 0.1.3 on npm registry
- Transport type stdio per server.schema.json
- Registry identifier doom-mcp (npm)
Community signal: 10 GitHub stars.
What problem does it solve?
You want proof that your agent’s MCP wiring actually invokes real tools, but most sample servers feel abstract and do not show a live interactive loop.
Who is it for?
Builders who already run Claude Code or Cursor with MCP and need a vivid, low-stakes integration test or demo before connecting business APIs.
Skip if: Teams shipping a commercial game, seeking ranked multiplayer infrastructure, or avoiding local game binaries and desktop dependencies.
What do I get? / Deliverables
After you install doom-mcp and add it to your MCP config, your agent can call DOOM-related tools over stdio and you have a working reference integration to copy for serious projects.
- Registered stdio MCP server entry pointing at doom-mcp
- Agent-visible MCP tools for DOOM interaction
- Working reference loop from agent tool call to in-game action
Recommended MCP Servers
Journey fit
MCP servers belong in Build because they extend what your coding agent can call during product work; DOOM here is an executable capability you register and invoke like any other tool. Agent-tooling is the right shelf for npm stdio servers that expose new actions to agents, distinct from shipping your own SaaS backend or frontend.
How it compares
MCP gameplay server and integration demo, not a Claude Code skill markdown workflow or a game distribution marketplace.
Common Questions / FAQ
Who is doom-mcp for?
Solo builders and small teams using MCP-enabled coding agents who want a hands-on way to verify tool calls and experiment with agent-driven control of an external app.
When should I use doom-mcp?
Use it during Build when you are configuring MCP servers, onboarding others to agent tooling, or prototyping automation patterns before you connect production APIs.
How do I add doom-mcp to my agent?
Install the npm package doom-mcp (v0.1.3), register it as a stdio MCP server in Claude Code, Cursor, or your client’s MCP settings, then restart the client so the DOOM tools appear in the tool list.