Rpg MCP Servers

🚀 RPG MCP Servers for Roo Code AI Dungeon

This project implements MCP (Model Context Protocol) servers to create an AI Dungeon-style RPG experience in Roo Code.

🚀 Quick Start

This project enables you to create an AI Dungeon-style RPG experience in Roo Code. After completing the setup, you can create new characters, manage inventory, conduct combat encounters, and track story progress, all with persistent state across sessions.

✨ Features

🎲 Latest Updates

• Fixed dice notation: Now supports 2d20kh1 (advantage) and 2d20kl1 (disadvantage).
• Added roll_check tool: Simplified ability/skill checks.
• Enhanced inventory: Added remove_item and update_item tools.
• Monster Management: Added tools for creating, getting, updating, and listing NPCs/monsters.
• Story and Quest Management: Added tools for saving story progress and managing quests.
• Corrected advantage/disadvantage: Properly implements D&D 5e rules.

See update-summary.md for full details.

🌟 Key Features

• Persistent State: Game data stored in SQLite database.
• Combat Engine: Full D20 system implementation.
• Separation of Concerns: Narrative (AI) vs Mechanics (MCP servers).
• Extensible: Easy to add new features.

📦 Installation

Prerequisites

Before you begin, ensure you have Roo Code installed and configured in your VS Code environment. Roo Code is the AI-powered coding assistant that will interact with these MCP servers.

• Install Roo Code:
  • From the VS Code Marketplace.
  • Or via CLI: code --install-extension RooVeterinaryInc.roo-cline.
• Configure AI Provider: After installation, add your AI model API keys (e.g., OpenAI, Anthropic) in the Roo Code extension settings.
• For more details on Roo Code, visit the Roo Code website or the official documentation.

Setup Instructions

1. Install dependencies for both servers:

   cd game-state-server
   npm install
   npm run build
   
   cd ../combat-engine-server
   npm install
   npm run build
   

2. Configure MCP Servers: Each server can be configured via environment variables or a .env file in its respective directory.

   • game-state-server:
     • DATABASE_PATH: Path to the SQLite database file (e.g., ./data/game.db). Default is ./data/game.db.
     • PORT: Port for the server to listen on (e.g., 3001). Default is 3001.
   • combat-engine-server:
     • PORT: Port for the server to listen on (e.g., 3002). Default is 3002.

   Example .env file for game-state-server:

   DATABASE_PATH=./data/my_game.db
   PORT=3001
   

3. Start the MCP Servers: To run the servers, navigate to their respective directories and use npm start or node dist/index.js. For example:

   cd game-state-server
   npm start
   # In a new terminal:
   cd ../combat-engine-server
   npm start
   

4. Roo Code Integration: To use these servers with Roo Code, you need to configure them in your mcp_settings.json file. This file is typically located at C:\Users\YOUR_USERNAME\AppData\Roaming\Code\User\globalStorage\rooveterinaryinc.roo-cline\settings\mcp_settings.json.

   Below are example configurations for each server. Adjust the cwd (current working directory) path to where you have cloned or placed the rpg-mcp-servers repository and built the servers.

   {
     "mcpServers": {
       // ... other servers ...
   
       "rpg-game-state": {
         "name": "rpg-game-state-server",
         "command": "node",
         "args": [
           "dist/index.js"
         ],
         "cwd": "PATH_TO_YOUR_PROJECT/rpg-mcp-servers/game-state-server",
         "enabled": true,
         "alwaysAllow": [
           "create_character",
           "get_character",
           "get_character_by_name",
           "list_characters",
           "update_character",
           "add_item",
           "get_inventory",
           "save_world_state",
           "get_world_state",
           "create_npc",
           "create_npc_group",
           "get_npc",
           "list_npcs",
           "update_npc",
           "remove_npc",
           "save_story_progress",
           "add_quest",
           "get_active_quests",
           "update_quest_state",
           "assign_quest_to_character"
         ]
       },
       "rpg-combat-engine": {
         "name": "rpg-combat-engine-server",
         "command": "node",
         "args": [
           "dist/index.js"
         ],
         "cwd": "PATH_TO_YOUR_PROJECT/rpg-mcp-servers/combat-engine-server",
         "enabled": true,
         "alwaysAllow": [
           "roll_dice",
           "attack_roll",
           "damage_roll",
           "saving_throw",
           "get_combat_log",
           "start_combat",
           "end_turn",
           "next_turn"
         ]
       }
       // ... other servers ...
     }
   }
   

   Note:

   • Replace PATH_TO_YOUR_PROJECT with the actual absolute path to the rpg-mcp-servers directory on your system. For example, if you cloned it to C:\projects\rpg-mcp-servers, then cwd for game-state-server would be C:/projects/rpg-mcp-servers/game-state-server.
   • The alwaysAllow arrays list tools that Roo Code can use without explicit user permission each time. You can customize this list.
   • The start_combat tool was present in your mcp_settings.json for rpg-combat-engine-server and has been added to this example. Ensure this tool is actually implemented in the server.

5. Create a custom mode for the AI Dungeon Master (e.g., using a dungeon-master-mode.json configuration within the AI Dungeon Experiment repository) to interact with these servers through Roo.

💻 Usage Examples

Basic Usage

Once setup is complete, you can:

• Create new characters
• Manage inventory
• Run combat encounters
• Track story progress
• All with persistent state across sessions!

📚 Documentation

Project Structure

• game-state-server/: SQLite-based persistent game state management
• combat-engine-server/: D&D-style combat mechanics and dice rolling