Play DOOM via MCP - works with Claude Code, Cursor, and any MCP client
Doom MCP server exists for a simple reason — assistants are far more useful when they can act on Doom directly instead of describing what you should do. Play DOOM via MCP - works with Claude Code, Cursor, and any MCP client.
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.
Once Doom is connected, these are the calls the assistant has available:
doom_start — Start or restart DOOM. Safe to call at any time — if a game is already running it restarts cleanly without needing a new sessiondoom_action — Advance the game. All listed actions are held simultaneously for the tick durationdoom_screenshot — Save a full-resolution 320x200 screenshot to the system temp directory and open it in the default image viewer. Does not advance the game (beyond adoom-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need one environment variable: DOOM_WAD_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Doom's toolset — doom_start, doom_action, doom_screenshot — is a fair guide to whether it matches your workflow. It is maintained by gunnargrosch; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| doom_start | Start or restart DOOM. Safe to call at any time — if a game is already running it restarts cleanly without needing a new session. |
| doom_action | Advance the game. All listed actions are held simultaneously for the tick duration. |
| doom_screenshot | Save a full-resolution 320x200 screenshot to the system temp directory and open it in the default image viewer. Does not advance the game (beyond a brief pause for the frame to settle). |
{
"mcpServers": {
"doom": {
"type": "stdio",
"command": "npx",
"args": ["-y", "doom-mcp"],
"env": {
"DOOM_WAD_PATH": "/path/to/DOOM1.WAD"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DOOM_WAD_PATH | Filesystem location the server is allowed to use. | Optional |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.