In-depth architectural comparison of the Cws MCP and Kiyas 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
Cws MCP
Browser Automation · Local stdio
Quality: 59/100 (Good) | Auth: OAuth 2.0
Kiyas
Browser Automation · Local stdio
Quality: 57/100 (Good) | Auth: other
Verdict Summary: Choose Cws MCP if you need specialized Browser Automation tools running via a local process. Choose Kiyas if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Cws MCP when:
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: CWS_CLIENT_ID, CWS_CLIENT_SECRET, CWS_REFRESH_TOKEN.
MCP server for Chrome Web Store extension management — 8 tools for upload, publish, status, staged rollout, and metadata updates.
Design-fidelity checks for AI agents: compare a Figma frame (or any design screenshot) against the rendered implementation and get structured discrepancies with CSS properties and severity. Resolves a natural-language component description to a URL + selector in your codebase, screenshots it with Playwright, and compares via vision AI using your existing Claude Code or Codex subscription — no API keys. 90% mutation recall, zero false positives on its golden eval set. npx -y kiyas-cli mcp
Category & Scope
Tools & Capabilities Breakdown
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.
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).
Cws MCP is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Kiyas belongs to Browser Automation using local stdio subprocess. Select Cws MCP when you need capabilities focused on browser automation and Kiyas when you require tools for browser automation.
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.