All servers / Gaming / World of Warcraft MCP server
World of Warcraft MCP server
MCP server exposing the World of Warcraft addon API (Blizzard generated documentation, FrameXML source, and Warcraft Wiki) across every wow-ui-source track — re
Tested by ConnectATDScore 84 out of 100. Tested 2026-11-19 on package version 0.2.16. Package: @nighthawk42/wow-api-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 18 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (3.6 seconds including download)
- Tools offered: 14
- Last published: 2026-11-17
- Weekly downloads (npm): 671
- License: MIT · Direct dependencies: 7
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
list_flavors1 of 1 parameter describedList every client flavor (wow-ui-source track) this server carries, with its game build, TOC interface version, upstream commit, and API counts. Use it to pick a `flavor` argument.
list_systems2 of 2 parameters describedList API systems (namespaces) for a flavor. Optionally filter by a case-insensitive substring of the system or namespace name.
search_api3 of 4 parameters describedFuzzy full-text search over API functions, events, and tables (enums/structures/constants) for a flavor. Searches names, systems, and documentation. Example queries: "C_Timer After", "unit health", "spell cooldown".
get_api2 of 2 parameters describedFull documentation for a function, event, or table by name — signature, typed arguments/returns/payload/fields, and cross-flavor availability. Accepts qualified names ("C_Timer.After"), bare names ("After"), or event literals ("PLAYER_ENTERING_WORLD"). Case-insensitive.
diff_api2 of 2 parameters describedCompare an API's existence and signature across flavors. Useful to check whether an API exists in a given client and whether its signature drifted between retail, classic, and the test realms.
diff_flavors4 of 6 parameters describedList APIs added or removed between two flavors — e.g. what the retail PTR gained over live, or what retail has that Classic Era lacks. Answers 'is this API safe to use on <client>' in bulk.
detect_wow_install1 of 1 parameter describedFind World of Warcraft installations on this machine and report, for each installed client (_retail_, _ptr_, _classic_, _classic_era_, ...), its Blizzard product code, exact game build, TOC interface number, and which API flavor to use for it. Call this first when working in an addon project so later API lookups target the right client. Build numbers come from `.build.info`, falling back to the client executable's version resource.
resolve_flavor4 of 4 parameters describedWork out which API flavor matches a game build, a TOC interface number, a Blizzard product code, or a path inside a WoW install / addon folder. Use this when you know what the addon targets ("## Interface: 110107", a `.toc` file, a build string) but not which flavor ID to query.
check_addon_compatibility1 of 1 parameter describedRead an addon's `.toc` files, resolve the flavor(s) it targets, and report the game build and API data the server will use for each. Point it at an addon directory or a `.toc` file.
search_wiki1 of 2 parameters describedSearch warcraft.wiki.gg — community documentation for the WoW addon API, UI widgets, events, TOC format, CVars, and guides. Returns page titles to use with get_wiki_page.
get_wiki_page2 of 2 parameters describedFetch a warcraft.wiki.gg page as markdown (cached ~24h). Useful pages: "TOC format", "World of Warcraft API", "Events", "Widget API", "API <FunctionName>" for per-function pages, "UIHANDLER <OnEvent>" for script handlers.
search_source4 of 6 parameters describedRegex search (POSIX ERE, via git grep) over Blizzard's FrameXML/AddOn UI source code for a flavor — the best way to learn how Blizzard implements UI patterns (templates, mixins, secure code). The first search per flavor downloads a ~200 MB source checkout and may take a minute.
list_source_files2 of 3 parameters describedList source files matching a path glob, e.g. `**/Blizzard_ActionBar*/**` or `**/*Mixin*.lua`. Useful for locating the right addon folder before reading files.
get_source_file2 of 4 parameters describedRead a file (or list a directory) from Blizzard's UI source for a flavor, with line numbers. Paths are repo-relative, e.g. "Interface/AddOns/Blizzard_UIParent/Blizzard_UIParent.lua".
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.