LLMMO Game 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., "@LLMMO Game Servercreate a new location called 'Enchanted Forest'"
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.
LLMMO Game Server
MCP server for LLM-driven text game state management. Exposes tools for managing players, locations, items, entities, and abstract concepts via the MCP protocol.
Built with FastAPI, FastMCP, Python 3.14.
Setup
Docker (recommended)
cp .env.example .env # adjust if needed
docker compose up --build appLocal
uv sync
uvicorn llmmo.main:app --reload --host 0.0.0.0 --port 8111Related MCP server: MythxEngine
Configuration
Environment variables (.env):
Variable | Default | Description |
|
| Server host |
|
| Server port |
|
| Game state storage directory |
|
| Allowed CORS origins |
|
| Allow credentials |
|
| Allowed HTTP methods |
|
| Allowed headers |
Authentication
Register at
GET /registerorPOST /registerGet an API key via
POST /auth/api-keys(JSON:{"username": "...", "password": "..."})Use the key as a Bearer token for MCP endpoints:
Authorization: Bearer <api_key>
Each user gets isolated game state stored in .state/<username_hash>/.
MCP Endpoint
MCP server is mounted at /mcp. Connect your MCP client to http://localhost:8111/mcp.
Data Model
Player — name, inventory (
item_id -> quantity), current locationLocation — name, description
Item — name, description (global, referenced by players)
Entity — name, description, optional location (NPCs, objects, monsters)
Abstract — name, description (events, topics, lore — not tied to locations)
All IDs are UUIDs. State is persisted as JSON files per user.
Development
uv sync --all-groups # install dev depsBefore commit: ruff (lint/format), mypy (type check).
This server cannot be deployed
Maintenance
Related MCP Connectors
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Cross-tool persistent memory and context for AI assistants over MCP.
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
Shared memory and actions for Claude, Kiro, OpenAI, Cursor, and other MCP-compatible AI clients.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to act as RPG Game Masters by managing campaign state including characters, inventory, quests, and logs through MCP tools. Supports campaign mutations and provides both MCP and HTTP API access to RPG session data.2-
- AlicenseNot gradedqualityAmaintenanceEnables AI to act as Game Master for tabletop RPGs with deterministic dice, five-tier outcomes, FitD-style stress, combat tracking, clocks, investigations, NPC relationships, and world generation via 134 tools over MCP.2MIT
- AlicenseNot gradedqualityBmaintenanceProvides MCP supervision and knowledge tools for controlling an LLM-driven Meridian 59 character, enabling durable goal management, persona configuration, and audited gameplay.MIT
- FlicenseBqualityBmaintenanceEnables AI agents and Claude to interact with the EmptySock game engine, exposing NavMesh, Physics, Scene, Save, and Actor systems as MCP tools.21-