MCP.Market

Doom MCP server

by gunnargrosch·io.github.gunnargrosch/doom-mcp·v0.1.3·13 stars

Play DOOM via MCP - works with Claude Code, Cursor, and any MCP client

C60/100grade C
What users say
No reviews yet
Be the first
Safety scan
C60/100

full report

Adoption
New

13 stars

Reviews

Write one

Nobody has reviewed Doom yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Doom tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-09-27 · same rubric, same numbers if you re-run it

2 medium
  • Code scan3 source files scanned15/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 198 days ago4/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (2)

  • mediumnpm install lifecycle script presentinstall.script
  • mediumnpm install lifecycle script presentinstall.script
    package.json: … "CHANGELOG.md" ], "scripts": { "postinstall": "node bin/postinstall.js" } } …
Overall 60/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Doom compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
60/100
higher than 15% of 48,255 servers
GitHub stars
13
more than 89% of 28,688 servers

Install Doom in Claude Code, Cursor or VS Code

Runs npx -y doom-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add doom-mcp -- npx -y doom-mcp
Add to Cursor

What the publisher says

From the Doom repository's README, as published. We do not edit it. Read it on GitHub

DOOM via MCP

Can it run DOOM? Yes - your AI coding assistant can run DOOM.

Play DOOM in Claude Code, Cursor, or any MCP-compatible client. The AI sees the game, fights demons, navigates levels, and reports what's happening - or you direct it move by move.

> Let's play DOOM!

  Starting E1M1 on medium difficulty...

  HP:100 Armor:0 | Pistol (key:2) | Ammo: 50b 0s 0r 0c | Kills:0 | E1M1
  No enemies in sight. Exploring the corridor ahead.

> Go forward and find some enemies

  Sprinting down the hallway... I can see an opening ahead.

  HP:100 Armor:0 | Pistol (key:2) | Ammo: 50b 0s 0r 0c | Kills:0 | E1M1
  ENEMIES IN SIGHT (aim for angle~0 then fire): Imp (HP:60) to your left (turn_left ~9) nearby

  There's an Imp to the left! Turning to face it...

> Shoot it!

  Aimed and firing!

  HP:100 Armor:0 | Pistol (key:2) | Ammo: 47b 0s 0r 0c | Kills:0 | E1M1
  ENEMIES IN SIGHT (aim for angle~0 then fire): Imp (HP:15) AHEAD close

  Hit! The Imp is wounded (HP:15). One more burst should finish it.

  HP:95 Armor:0 | Pistol (key:2) | Ammo: 44b 0s 0r 0c | Kills:1 | E1M1
  ITEMS: Stimpack (+10 HP) slightly to your right (turn_right ~4) point-blank (~3 ticks fwd+run to reach)
  1 kill! Want to see a screenshot?

Read the blog post for the full story.

Table of Contents

  • How It Works
  • Quick Start
  • Play Modes
  • Tools Reference
  • Configuration
  • FAQ
  • Architecture
  • Development
  • Credits
  • License

How It Works

A Rust MCP server embeds the real DOOM engine (doomgeneric) directly via FFI. No emulation, no child processes. Each tool call advances the game by a number of ticks and returns:

  1. Game state - HP, armor, ammo, kills, position, current weapon
  2. Enemy intel - visible enemies with human-readable direction, distance, and HP
  3. Nearby items - health, ammo, armor, weapons within pickup range
  4. Doors and switches - interactable linedefs detected within range
  5. Frame image - small PNG thumbnail for the AI's vision

The AI uses this information to navigate, fight, and explore. You can direct it or let it play autonomously.

graph LR
    A[MCP Client] -->|doom_start| B[doom-mcp binary]
    A -->|doom_action| B
    A -->|doom_screenshot| B
    B -->|FFI| C[doomgeneric C engine]
    C -->|frame buffer| B
    B -->|game state + PNG| A

Quick Start

1. Register with your MCP client

Claude Code:

claude mcp add doom --scope user -- npx -y doom-mcp

Cursor, Windsurf, or any MCP client - add to .mcp.json:

{
  "mcpServers": {
    "doom": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "doom-mcp"]
    }
  }
}

2. Play

Open a new session and say:

"Let's play DOOM"

The AI will ask which mode you want, start the game on E1M1, and begin playing.

Play Modes

Tools Reference

doom_start

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Doom: common questions

Is Doom MCP server safe?
With care: it is graded C, so read the findings first (60/100). Read the Doom safety report
How do I install Doom?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Doom need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Doom maintained?
The last commit was 235 days ago (2026-03-13). The latest release is v0.1.3.
How does Doom compare with other MCP servers?
safety score 60/100 (higher than 15% of 48,255 servers); github stars 13 (more than 89% of 28,688 servers). Full comparison.