In-depth architectural comparison of the Hub MCP and Cws MCP 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
Cws MCP
Developer Tools · Local stdio
Quality: 59/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Hub MCP if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Cws MCP 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, Cws MCP belongs to Developer Tools using local stdio subprocess. Select Hub MCP when you need capabilities focused on developer tools and Cws MCP 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
Cws MCP Tools (8)
upload
Upload a ZIP file to update an existing Chrome Web Store item draft. Note: Creating new items via API is not supported in v2 — use the Developer Dashboard to create new items.
publish
Publish an extension to Chrome Web Store. Supports immediate publish, staged publish, initial deploy percentage, and skip-review.
status
Fetch the current status of an extension on Chrome Web Store. Returns published/submitted revision status, deploy percentage, version, takedown/warning flags, and last upload state.
cancel
Cancel a pending submission on Chrome Web Store. Can be used to cancel an item currently in review.
deploy-percentage
Set the published deploy percentage for staged rollout on Chrome Web Store. The new percentage must be higher than the current target. Only available for items with 10,000+ seven-day active users.
get
Get the current metadata of a Chrome Web Store item (v1.1 API). Returns title, description, category, and other listing fields. Note: v1 API is deprecated and will be removed after Oct 15, 2026.
update-metadata
Update the store listing metadata of a Chrome Web Store item (v1.1 API). Supports both common fields and raw metadata payload for advanced fields. Note: v1 API is deprecated and will be removed after Oct 15, 2026. Use update-metadata-ui as an alternative.
update-metadata-ui
Update listing metadata via Chrome Web Store dashboard UI automation (Playwright). Use this when API metadata updates are not reflected, or as the primary metadata update method since the v1 API is deprecated.