A complete local MCP (Model Context Protocol) server for managing a standalone WoW private server. Built and tested for World of Warcraft repacks (specifically Cata/MoP) with MySQL, but works with any repack when correctly configured.

In short: if you can do it in-game as a GM or via the database, the agent can do it for you.

• What Can the Agent Do?
• Why MCP Instead of Raw Credentials?
• Demo Videos
• Quick Start
• Dynamic Schema (Any Expansion)
• Available Tools (76 total)
• Database Backups
• Updating from an Older Release
• Prerequisites
• Project Structure

Once connected, an AI agent (Claude, Gemini, Antigravity, or any MCP-compatible client) gets full control over your WoW server through natural language. No need to touch the database, config files, or console manually — just ask.

You could just tell your AI agent "here's my workspace, my DB password is ascent, and RA is on port 3443" — and it would technically figure things out. But here's why a dedicated MCP server is significantly better:

TL;DR: The MCP server turns your AI agent from a "smart intern who needs to Google everything" into a "senior dev with a custom toolkit".

📁 YourRepackFolder\
├── 📁 Database\
├── 📁 wow-server-mcp\   ← clone here
└── 📁 Repack\

cd "C:\path\to\YourRepackFolder"
git clone https://github.com/timoinglin/wow-server-mcp.git

Double-click install.bat inside the wow-server-mcp folder.
It will automatically:

• Check for Node.js and install it via winget if missing
• Copy example.config.json → config.json
• Run npm install
• Build the TypeScript project (npm run build)

Manual alternative:

cd wow-server-mcp
npm install
npm run build

Open config.json and update:

• Database credentials — default: root / ascent on localhost:3306
• RA credentials — create a GM account first (level 3+), then set username/password
• Server paths — should be correct for the default repack layout

In Repack/worldserver.conf:

Ra.Enable = 1
Ra.IP     = 127.0.0.1
Ra.Port   = 3443

Then restart the worldserver and set the matching credentials in config.json under remote_access.

Replace <REPACK_PATH> with the absolute path to your repack folder.
Use forward slashes / even on Windows (e.g. C:/Games/mop_repack/MOPFREE).

🟣 Antigravity (VSCode extension)
File: C:\Users\<you>\.gemini\antigravity\mcp_config.json

{
  "mcpServers": {
    "wow-server": {
      "command": "node",
      "args": ["<REPACK_PATH>/wow-server-mcp/dist/index.js"],
      "cwd": "<REPACK_PATH>/wow-server-mcp"
    }
  }
}

🟠 Claude Desktop
File: C:\Users\<you>\AppData\Roaming\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "wow-server": {
      "command": "node",
      "args": ["<REPACK_PATH>/wow-server-mcp/dist/index.js"],
      "cwd": "<REPACK_PATH>/wow-server-mcp"
    }
  }
}

🔵 VS Code (GitHub Copilot / Cline / OpenClaw / other MCP extensions)
File: .vscode/mcp.json inside your project, or via the extension's settings UI — check your extension's docs for the exact location. The JSON block is the same as above.

After saving, restart your AI client and the wow-server will appear in the available tools list.

The server utilizes a Dynamic Schema Mapping system, meaning it can automatically adapt to Mists of Pandaria, Cataclysm, Wrath of the Lich King, or Legion repacks, even when database column names are different.

To configure the MCP for your specific repack:

1. Complete the Quick Start connection steps above so the AI can connect to your database.
2. Ask your AI Assistant to "Run the discover_schema tool".
3. The AI will scan your database (INFORMATION_SCHEMA) and generate a schema_override.json file perfectly tailored to your repack's database structure.
4. Tell the AI to update your config.json to include "schemaOverride": "schema_override.json".
5. Restart the AI client, and you are fully compatible!

The server includes a powerful built-in create_db_backup tool that securely interfaces with your mysqldump.exe. All backups generated by the AI agent are cleanly placed into a local backups/ directory located right beside the wow-server-mcp folder. The tool supports three levels of flexibility:

• Full Backups — specify auth, characters, and world for a complete backup file.
• Single Database Backups — dump an entire single database to a .sql file.
• Custom / Fine-Grained Backups — target specific tables (e.g. ['account']) with a SQL WHERE clause (e.g. username = 'kneuma') to isolate exactly the data you need.

If you already have a previous version installed, updating is simple:

cd wow-server-mcp
git pull
npm install
npm run build

Then restart your AI client (Antigravity, Claude Desktop, etc.) to reload the MCP server with the new code.

• Node.js 18+ (tested with v24.13.0)
• MySQL running (via the repack's MySQL.bat)
• Worldserver running (for RA commands)
• A GM account with level 3+ (for RA access)

wow-server-mcp/
├── src/
├── dist/                     — Compiled JavaScript
├── install.bat               — One-click installer (double-click me!)
├── install.ps1               — Installer script (called by install.bat)
├── config.json               — Your local config (never commit this)
├── example.config.json       — Template config
└── package.json

• 🚀 Project Rebrand: Renamed from emucoach-mcp to wow-server-mcp.
• ♻️ Refactored All Files: Updated internal identifiers, identifiers, documentation, and installer scripts for the new name.
• 📦 GitHub Release: Automated release under the new repository name.

• 🚀 Dynamic Schema Mapping: Implemented the discover_schema tool to automatically detect and map database structures (WotLK, Cata, Legion, etc.)!
• ♻️ Refactored All Tools: Account, NPC, Quest, Loot, and Lookup tools now fully utilize the dynamic schema resolver.
• 📝 Added full cross-expansion setup documentation to README.

• 🐛 Fixed quest_template column name mismatches in get_quest_rewards and create_quest
• 🐛 Fixed npcflag inconsistency for quest giver/ender relations
• 📝 Updated README version shield

• 🐛 Fixed SQL compatibility with older MySQL versions (LIMIT ? in prepared statements)
• 🐛 Fixed reserved keyword escaping for rank, type, Type columns
• 🐛 Fixed spell_dbc schema mismatch (Comment column instead of SpellName1)
• 🐛 Fixed game_event schema mismatch (eventEntry instead of entry)
• 📝 Improved README with MCP badges, "Why MCP?" section, and capability table
• ✅ All 72 tools verified operational

• 🐉 Added NPC development tools (13 tools)
• 📜 Added Quest development tools (7 tools)
• 💎 Added Loot & world data tools (8 tools)

• 🎉 Initial release with core tools across 7 categories