wow-addon-api-mcp
Related Servers
Alternatives to wow-addon-api-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.10 npm13MIT
- AlicenseAqualityAmaintenanceMCP server for writing World of Warcraft addons, providing in-game Lua API references, Blizzard's UI source code, and game asset data to AI assistants.19566 npm5MIT
- 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-
- FlicenseNot gradedqualityFmaintenanceA comprehensive MCP server that wraps the complete World of Warcraft retail API into 197 tools for Game Data and Profile information. It enables users to query character statistics, achievements, collections, and game mechanics across all global regions and locales.9-
- AlicenseAqualityBmaintenanceAn MCP server that exposes World of Warcraft character data from the Blizzard API, offering read-only tools for character summaries, equipment, Mythic+ scores, realm lookup, and other character sub-resources.5MIT
TDQS
Scored across 17 tools
Each tool has a distinct target (API, engine contract, resource, runtime resource, namespace, widget, enum, event, version diff), and descriptions are explicit. Some ambiguity remains because lookup_api is a broad superset of get_event/get_enum/get_widget_methods and search_api overlaps conceptually with search_resources, though the exact-vs-fuzzy nature is clarified.
Names are consistently snake_case verb_noun combinations such as lookup_api, lookup_resource, search_api, search_resources, and diff_versions. The verb set (get/lookup/search/list/compare/diff) is not perfectly uniform, but each operation type follows a recognizable pattern.
Seventeen tools is slightly above the typical 3-15 range, but the domain is broad enough to justify dedicated lookups, searches, comparisons, and history tools. None of the tools feel redundant; each addresses a separate exploration need.
The read-only catalog surface is comprehensive: exact lookups, fuzzy searches, versions, namespace listing, runtime resources, migration guidance, restrictions, and multi-version comparison/history are all covered. There are no obvious dead ends or missing core operations for the stated purpose.