In-depth architectural comparison of the Hub MCP 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
Hub MCP
Developer Tools · Remote HTTP/SSE
Quality: 77/100 (Great) | Auth: API Key required
Warcraft III Map Tools
Developer Tools · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Hub MCP if you need specialized Developer Tools tools running via a hosted cloud SSE transport. 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 Hub MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: HUB_PAT_TOKEN, MCP_AUTH_TOKEN.
Hub MCP is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Warcraft III Map Tools belongs to Developer Tools using local stdio subprocess. Select Hub MCP when you need capabilities focused on developer tools and Warcraft III Map Tools when you require tools for developer tools.
Number of documents to skip for pagination (number, optional)
images
Filter on image names (string, optional)
operating_systems
Filter on operating systems (string, optional)
order
Change the ordering of results (string, optional)
size
Maximum number of results to return (number, optional)
sort
Sort results by search field (string, optional)
+23 more tools listed on main page
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
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.