In-depth architectural comparison of the Mcp Kodi and Shelly Smart Home 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
Mcp Kodi
Home Automation · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Shelly Smart Home
Home Automation · Local stdio
Quality: 27/100 (Emerging) | Auth: No auth required
Verdict Summary: Choose Mcp Kodi if you need specialized Home Automation tools running via a hosted cloud SSE transport. Choose Shelly Smart Home if your workspace requires Home 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 Mcp Kodi when:
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).
You have access to required keys: KODI_HOST, KODI_PORT, KODI_USERNAME, KODI_PASSWORD, DEFAULT_INSTANCE.
Primary tools included: Supports multiple Kodi instances with configurable keys, 16 dedicated tools covering transport, volume, search, queue, and history, RPC escape hatch for any Kodi JSON-RPC method.
Control a Kodi media player over its JSON-RPC API — transport, volume, library search, queue management, and playback history. 16 tools, targetable across multiple Kodi instances. Written in C on the GLib stack; builds from source (autotools / .deb).
Local-first MCP server for Shelly smart-home devices (Gen1-Gen4): control, energy, automation.
Mcp Kodi is categorized under Home Automation and uses a remote streaming HTTP/SSE transport. In contrast, Shelly Smart Home belongs to Home Automation using local stdio subprocess. Select Mcp Kodi when you need capabilities focused on home automation and Shelly Smart Home when you require tools for home automation.