📡 MCP Radar

Dicklesworthstone/dwarf_fortress_mcp

A semantic, transactional, replayable MCP control plane that lets autonomous AI agents operate Dwarf Fortress as a long-lived civilization. Safe-Rust phase-0B scaffold: MVCC world state, witnessed sem

4 stars
0 forks
Rust
momentum ▲ 40.0
created 2026-08-29
on radar since 2026-08-30
ai-agentsautonomous-agentscontrol-planedeterministicdfhackdwarf-fortressgame-automationllm-toolsmcpmodel-context-protocolmulti-agentmvccrustsafe-rusttransactional
View on GitHub ↗

About dwarf_fortress_mcp

A semantic, transactional, replayable control plane that lets autonomous agents operate Dwarf Fortress as a long-lived civilization rather than click through it as a brittle user.

Status: owned MCP transport laboratory on the deep architecture lock (Phase 0C). The MCP plane is the owned fastmcprust sibling — modern-only MCP 2026-07-28, pinned to an exact upstream revision and dogfooded upstream — exposing the frozen 11-tool fortress. waist over stdio against the deterministic laboratory. The substrate commitments stand: multi-version world state, witnessed semantic transactions, canonical graph decisions, root-last immutable publication, ATP-backed state/evidence movement, a closed dependency universe, and local-only qualification. There is still no live DFHack adapter. See IMPLEMENTATIONSTATUS.md before interpreting any target-state prose as implemented behavior.

The originating observation was simple: Dwarf Fortress is almost the ideal environment for long-horizon agents, yet there was no efficient MCP server through which Codex, Claude Code, or similar systems could control the game while monitoring state and progress. A naive answer would expose dozens of DFHack commands and screenshots as MCP tools. That would work just well enough to become dangerous: observations would be expensive and incomplete, commands would acknowledge dispatch rather than prove success, retries could duplicate effects, version drift would silently corrupt assumptions, and no one could reconstruct why the fortress ended up in its present state.

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/Dicklesworthstone--dwarf_fortress_mcp.html)

Related MCP servers

naw103/foremerge

Catch intent conflicts before code conflicts. The open-source coordination protocol for coding agents, built above Git.

⭐ 32Rust
harlixay7/AgentXFlow

Authoritative multi-agent software engineering coordinator with isolated Git worktrees, write scope locking, test verification, and serialized merge queue. (v0.1.0-beta).

⭐ 6Rust
systempromptio/systemprompt-demo

AI Governance Infrastructure — open gateway demo. Self-hosted systemprompt.io gateway in a single Rust binary: policy, audit trails, and cost attribution on every AI request, with the Systemprompt Bri

⭐ 3Rust
omaekumiko2-create/kru

Local-first MCP password and credential manager for AI agents. Use passwords, API keys, SSH identities, and TOTP without exposing hidden plaintext to the model.

⭐ 88Rust
menot-you/n-memory

Memory your agent can trust — every answer carries its source; when it doesn't know, it says so. Hermetic, local, MCP.

⭐ 5Rust
Kaseban/baton

Convert AI coding sessions between Claude Code, Codex, OpenCode, Zed, Aider, Gemini CLI, Cursor, Cline & more — lossless, round-trip tested. MCP server + CLI.

⭐ 4Rust

📬 Get the weekly radar in your inbox

The top new MCP servers of the week, every Monday. No spam, unsubscribe anytime.