🐉 New from me — WOW Legends: a free WotLK 3.3.5a repack

Run your own living Wrath of the Lich King (3.3.5a) world in a few clicks — hundreds of AI-driven bots, an AI companion that chats back, hardcore mode, and a one-click installer.

▶ Check it out → wow-legends.eu

WoW Server MCP

A local MCP server that lets any MCP-compatible AI client (Claude, Codex, Cursor, etc.) manage a standalone World of Warcraft private server. Built and tested for Cata / MoP repacks with MySQL — works with any repack once configured.

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

💛 Using the WoW Server MCP? It's free and open-source, built and maintained in spare time. If it's saved you hours of server admin — or you'd like to see it keep growing — a coffee genuinely helps. See Support the Project.

Table of Contents

• What the Agent Can Do

• Why an MCP Instead of Raw Credentials?

• Demo Videos

• Quick Start

• Dynamic Schema (Any Expansion)

• Available Tools (82 total)

• Bug-Hunting / DB Integrity

• Database Backups

• Updating

• Prerequisites

• Project Structure

• Releases

• Support the Project

Related MCP server: ItchWHMMCP

What the Agent Can Do

Once connected, the AI gets full control over your WoW server through natural language.

Why an MCP Instead of Raw Credentials?

You could hand the AI your DB password and RA port and let it figure things out — but a dedicated MCP is significantly better:

Demo Videos

Quick Start

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

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

1. Install & Build

Easy (Windows): double-click install.bat. It checks for Node.js (installs via winget if missing), copies example.config.json → config.json, runs npm install, and builds.

Manual (any OS):

cd wow-server-mcp
cp example.config.json config.json   # Windows: copy example.config.json config.json
npm install
npm run build

2. Configure

Edit config.json:

• Database credentials — defaults to root / ascent on localhost:3306

• RA credentials — set after creating a GM account (level 3+)

• Server paths — only change if your folder layout differs from the recommended one above

3. Enable Remote Access (RA) on the Worldserver

In Repack/worldserver.conf:

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

Restart the worldserver and put the matching credentials in config.json under remote_access.

4. Add to Your AI Client

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

After adding the config, restart your AI client; wow-server will appear in its tool list.

🟠 Claude Desktop

Open Settings → Developer → Edit Config, or edit the file directly:

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

If the file already exists, merge the "wow-server" entry into the existing mcpServers object. Quit Claude from the tray icon (right-click → Quit) before relaunching — closing the window leaves it running in the background.

🟢 Claude Code (VS Code extension / CLI)

Easiest — one command:

claude mcp add wow-server -s user -- node "<REPACK_PATH>/wow-server-mcp/dist/index.js"

-s user makes the server available in every project. Use -s project to scope it to the current workspace (writes .mcp.json to the project root).

Or edit the project-scoped file by hand, <your-project>/.mcp.json:

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

Reload VS Code (Ctrl+Shift+P → "Developer: Reload Window"). For project-scoped servers, Claude prompts once to approve — click approve. Verify with /mcp inside Claude Code.

🔷 Codex CLI

Add to ~/.codex/config.toml (create the file if it doesn't exist):

[mcp_servers.wow-server]
command = "node"
args = ["<REPACK_PATH>/wow-server-mcp/dist/index.js"]

Start a fresh codex session. Tools appear under the namespace mcp__wow-server__*.

🟣 Antigravity (Google's VS Code-based agent IDE)

Easiest — built-in UI: click the Agent Manager icon in the top bar, then the ⋯ menu → MCP Servers and add a new server with:

• Command: node

• Args: <REPACK_PATH>/wow-server-mcp/dist/index.js

Or edit the config file directly at 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"
    }
  }
}

Dynamic Schema (Any Expansion)

The MCP ships with the Cata / MoP TrinityCore schema baked in, but it can adapt to any repack — Wrath, Cataclysm, MoP, Legion, AzerothCore variants — by overriding column names.

To set it up for a non-default core:

1. Complete the Quick Start so the AI can reach your database.

2. Ask the AI to run the discover_schema tool. It scans INFORMATION_SCHEMA and writes a schema_override.json tailored to your DB.

3. The default example.config.json already sets "schemaOverride": "schema_override.json" — so if you copied that as your config.json, the file is picked up on the next start. If your config.json doesn't have that line, add it.

4. Restart your AI client. Look for Schema override loaded from … in the MCP server's stderr to confirm.

Available Tools (82 total)

Config Management (4)

Database Access (7)

RA Commands (2)

Process Management (10)

Account Management (7)

Server Config Files (5)

Lookup & Editing (13)

NPC Development (13)

Quest Development (7)

Loot & World Data (8)

Forensics / DB Integrity (6) — new in 1.4.0

See docs/BUGHUNT.md for the false-positive playbook these tools were designed around.

Bug-Hunting / DB Integrity

The forensic tools above were built to answer one question: "is this DB anomaly actually a bug, or does the core handle it some other way?" Common pitfalls they prevent:

• Currencies aren't items. Negative item IDs in loot tables point to Currency.dbc, not item_template. inspect_loot_table labels them explicitly.

• Magic action_menu_id values aren't menus. 1048576 = GOSSIP_OPTION_BATTLEFIELD (Wintergrasp queue), 2097152 = auctioneer, etc. inspect_gossip_chain flags all known sentinels.

• SmartAI bypasses missing gossip rows. event_type = 62 (GOSSIP_SELECT) fires when a player clicks an option regardless of whether the destination menu row exists. inspect_creature warns when both gossip_menu_id and SmartAI gossip handlers are present.

• ScriptName implies C++ handling. A non-empty creature_template.ScriptName means a compiled handler exists on the running server. check_scriptname verifies whether the name resolves in the configured core source tree.

• Cherry-picking rows is misleading. A loot table with 12 working + 2 broken rows is not "broken". inspect_loot_table always shows the full picture.

If you're running a hunt at scale, read docs/BUGHUNT.md first — it includes pre-built find_orphan_refs queries for the most productive sweeps.

To enable check_scriptname, add to config.json:

{
  "core_source_path": "C:/path/to/your/SkyFire_or_TrinityCore/checkout"
}

Database Backups

create_db_backup invokes mysqldump securely (no shell, password via MYSQL_PWD env, identifier validation on table names) and writes to a backups/ directory next to wow-server-mcp. Three modes:

• Full backup — pass all three databases (auth, characters, world) for a complete dump.

• Single database — pass one database to dump its entire schema.

• Targeted backup — pass one database + specific tables + an optional WHERE clause (e.g. dump account rows for username = 'kneuma').

Updating

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

Then restart your AI client to load the new code.

Prerequisites

• Node.js 18+ (tested through v24.x)

• MySQL running (the repack's MySQL.bat works)

• Worldserver running (required for RA-based tools)

• A GM account with level 3+ (for RA authentication)

Project Structure

wow-server-mcp/
├── src/                   — TypeScript source
├── dist/                  — Compiled JS (generated by `npm run build`)
├── install.bat            — One-click Windows installer
├── install.ps1            — Installer script (called by install.bat)
├── example.config.json    — Template config (commit-safe)
├── config.json            — Your local config (gitignored, has credentials)
└── package.json

Releases

Per-version release notes live on the GitHub Releases page.

Support the Project

This project is free and open-source, built and maintained in spare time. If it's saved you time setting up or running your server — or you'd just like to see it keep growing — a coffee is hugely appreciated and helps keep the WoW repack tools maintained and improving.

Every contribution also funds more free tools for the MoP / Cata repack community — thank you! 💛