McpProxy vs Kiyas — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
McpProxy vs Kiyas
In-depth architectural comparison of the McpProxy 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
McpProxy
Browser Automation · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Kiyas
Browser Automation · Local stdio
Quality: 57/100 (Good) | Auth: other
Verdict Summary: Choose McpProxy 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 McpProxy when:
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: IDE_PORT, HOST, LOG_ENABLED.
Primary tools included: Proxies MCP requests to JetBrains IDEs via local webserver, Supports configuration of IDE host and port, Enables logging via environment variable.
A model context protocol server to work with JetBrains IDEs: IntelliJ, PyCharm, WebStorm, etc. Also, works with Android Studio
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
McpProxy Tools (5)
Proxies MCP requests to JetBrains IDEs via local webserver
Supports configuration of IDE host and port
Enables logging via environment variable
Compatible with VS Code and Claude Desktop MCP clients
Supports external connections with proper IDE settings
Kiyas Tools (6)
Figma frame or custom image input
AI component and selector resolution
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).
McpProxy is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Kiyas belongs to Browser Automation using local stdio subprocess. Select McpProxy when you need capabilities focused on browser automation and Kiyas when you require tools for browser automation.