Debmatic Mcp vs Mockd — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Debmatic Mcp vs Mockd
In-depth architectural comparison of the Debmatic Mcp and Mockd 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
Debmatic Mcp
Home Automation · Local stdio
Quality: 51/100 (Good) | Auth: other
Mockd
Home Automation · Remote HTTP/SSE
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Debmatic Mcp if you need specialized Home Automation tools running via a local process. Choose Mockd if your workspace requires Home Automation integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Debmatic Mcp when:
You need dedicated capabilities in the Home Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: CCU_HOST, CCU_PASSWORD, MCP_ALLOWED_HOSTS, MCP_ALLOWED_ORIGINS.
Primary tools included: 25 MCP tools, HomeMatic JSON-RPC and HM-Script API access, Device discovery and type resolution.
You need dedicated capabilities in the Home Automation domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Supports 7 protocols in one binary with zero dependencies, Stateful CRUD API mocking with multi-step flows, Chaos profiles, fault injection, and circuit breakers.
Control a HomeMatic / debmatic CCU (eq-3 home automation) over its JSON-RPC and HM-Script APIs — switch and dim actuators, read sensors, system variables and service messages, run programs, and manage rooms, functions, channel links and device assignments. 25 tools over HTTP or stdio; runs locally against your own CCU.
Multi-protocol API mock server with 18 MCP tools. Mock HTTP, GraphQL, gRPC, WebSocket, MQTT, SSE, and SOAP APIs with chaos engineering, stateful CRUD, 8 import formats (OpenAPI, Postman, HAR, WireMock, cURL, Mockoon, WSDL), and deterministic seeded responses.
Category & Scope
Tools & Capabilities Breakdown
Debmatic Mcp Tools (6)
25 MCP tools
HomeMatic JSON-RPC and HM-Script API access
Device discovery and type resolution
Value conversion and session management
stdio and standalone HTTP modes
Support for debmatic, CCU3, and OpenCCU
Mockd Tools (6)
Supports 7 protocols in one binary with zero dependencies
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).
Debmatic Mcp is categorized under Home Automation and uses a local stdio subprocess. In contrast, Mockd belongs to Home Automation using remote streaming HTTP/SSE transport. Select Debmatic Mcp when you need capabilities focused on home automation and Mockd when you require tools for home automation.