Hated Wow Mcp

An MCP server for writing World of Warcraft addons. Free and open source.

It gives your AI assistant three things it otherwise guesses at: the in-game Lua API for the client you are targeting, Blizzard's own shipped UI source so it can see how the game itself does something, and the game's art and file data so texture references are real rather than invented.

20 tools. Setup for Claude Code, Claude Desktop, Cursor, Cline, Antigravity, Codex and VS Code is below, and anything else that speaks MCP works too. Or browse them in a local web UI with no AI at all.

☕ Support this project

Hated WoW MCP is free and always will be. If it saves you time, you can buy me a coffee — it genuinely helps keep it maintained through patch cycles.

buymeacoffee.com/rdygaming

Everything here is about code that runs inside the client. There is no Battle.net web API in this server — no armory lookups, no auction house.

Quick start

Requires Node 20+. Nothing to clone, nothing to build.

Claude Code

claude mcp add wow -- npx -y hated-wow-mcp

Add -s user to make it available in every project instead of just the current one. Verify with claude mcp list.

Claude Desktop

Edit your config file:

Windows Store install? If that path doesn't exist, look under %LOCALAPPDATA%\Packages\Claude_*\LocalCache\Roaming\Claude\ instead.

Add the mcpServers block. If the file already has other keys, keep them — merge this in rather than replacing the file:

{
  "mcpServers": {
    "wow": {
      "command": "npx",
      "args": ["-y", "hated-wow-mcp"],
      "env": {
        "WOW_DEFAULT_FLAVOR": "mainline"
      }
    }
  }
}

Then fully quit Claude Desktop from the system tray and reopen it — closing the window is not enough, and the config is only read at startup.

Other clients

It is a standard stdio MCP server, so any MCP client can run it. What differs is the config format. The shapes below come from each client's own documentation.

VS Code uses a different top-level key from everyone else:

{
  "servers": {
    "wow": { "command": "npx", "args": ["-y", "hated-wow-mcp"] }
  }
}

Codex reads TOML, not JSON. Either run codex mcp add wow -- npx -y hated-wow-mcp or add this to ~/.codex/config.toml:

[mcp_servers.wow]
command = "npx"
args = ["-y", "hated-wow-mcp"]
env = { WOW_DEFAULT_FLAVOR = "mainline" }
startup_timeout_sec = 30

Raise startup_timeout_sec from Codex's default of 10. The first npx run has to download the package, which took about 9 seconds on a fast connection and would time out on a slower one. Claude Code has the same knob as MCP_TIMEOUT.

On Windows, some clients start servers without a shell, and plain npx then fails to launch at all (ENOENT). Wrap it in cmd:

{
  "mcpServers": {
    "wow": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "hated-wow-mcp"]
    }
  }
}