In-depth architectural comparison of the MCP Graphql and Warcraft III Map Tools MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Graphql
Developer Tools · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Warcraft III Map Tools
Developer Tools · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose MCP Graphql if you need specialized Developer Tools tools running via a local process. Choose Warcraft III Map Tools if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Graphql when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
This tool retrieves the GraphQL schema. Use this first if you don't have access to the schema as a resource.
query-graphql
Execute GraphQL queries against the endpoint. By default, mutations are disabled unless `ALLOW_MUTATIONS` is set to `true`.
Warcraft III Map Tools Tools (80)
asset_list
List the asset paths an icon or model object field can actually be set to, from the map's own imported files and from the base game.
audit_ability
Tells you, per ability, PASS or the exact broken link across a placed hero's whole runtime chain, far deeper than audit_hero, which only proves a cast...
audit_fidelity
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
MCP Graphql is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Warcraft III Map Tools belongs to Developer Tools using local stdio subprocess. Select MCP Graphql when you need capabilities focused on developer tools and Warcraft III Map Tools when you require tools for developer tools.
Tells you whether a ported object's data came across faithfully, by comparing it and its whole custom-object dependency closure between the SOURCE map it...
audit_hero
Tells you whether a placed hero's abilities are actually wired up in the map's script, not merely present as object data.
audit_map
Behavioural audit of a map's object data, read-only.
audit_readiness
Tells you whether a placed hero's script would actually RUN correctly, not just fire, the gap audit_hero cannot see since it only proves a cast reaches a...
bundle_unit
Resolve everything a unit depends on, the porting preview.
camera_add
Add a camera at a target position and save the edited map to out_path.
camera_list
List the map's cameras (war3map.w3c).
camera_remove
Remove a camera and save the edited map to out_path.
camera_set
Set a field on a camera and save the edited map to out_path.