Hated WoW MCP
Related Servers
Alternatives to Hated WoW MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP server that gives AI coding assistants access to the World of Warcraft addon API documentation, FrameXML/AddOn UI source code, and the Warcraft Wiki across all four client flavors.912 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes structured World of Warcraft API data (functions, deprecated replacements, enums, events, widget methods) to AI agents, enabling querying and exploration of WoW API without wiki parsing.12 npm13MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for World of Warcraft that provides 26 tools for accessing characters, guilds, realms, game data, and auction house info via Blizzard's Battle.net APIs. It enables natural-language queries for character audits, Mythic+ reviews, market analysis, and more.-
- AlicenseAqualityAmaintenanceA version-aware MCP server that provides the World of Warcraft retail AddOn API with pinned documentation snapshots, enabling lookups, searches, comparisons, and diffs of APIs across patches.17257 npmApache 2.0
- FlicenseNot gradedqualityDmaintenanceMCP server that gives LLMs live access to warcraft.wiki.gg API documentation with behavioral notes, restrictions, and patch history for World of Warcraft APIs.1-
- AlicenseNot gradedqualityCmaintenanceA local MCP server that lets any MCP-compatible AI client manage a standalone World of Warcraft private server, including server control, database operations, NPC/quest/loot management, and more.1MIT
TDQS
Scored across 19 tools
Most tools have clear distinct purposes (API search vs events vs types, UI grep vs read file vs templates, lint vs validate). Minor overlap exists between wow_file_search and wow_icon_search (both find icons), and wow_api_stats and wow_data_status both report sync state, but descriptions clarify the differences.
All names use the wow_ prefix and snake_case, but there is a mix of verb-led names (wow_api_search, wow_ui_read_file, wow_addon_scaffold) and noun-led names (wow_install_info, wow_data_status, wow_api_stats). Overall the pattern is predictable and consistent enough to be intuitive.
At 19 tools, the count exceeds the typical 3-15 well-scoped range, but the scope is broad: API reference, UI source inspection, asset search, validation, and scaffolding for WoW addons. Each tool serves a distinct need, making the count reasonable for the domain.
The toolset covers the full addon development lifecycle: researching APIs and events, inspecting Blizzard UI source, searching assets, validating Lua/XML/TOC files, linting, and scaffolding new addons. There are no obvious gaps that would block an agent from completing common tasks.