"Home Assistant" matching MCP servers:

AI sysadmin for Home Assistant that provides entity health analysis, automation diagnostics, dashboard analysis, configuration search, and system health scoring via the Model Context Protocol.

A read-only Kubernetes MCP server that enables developers to inspect app status, view pod events, and fetch container logs from dev clusters without requiring full kubectl access.

Enables AI assistants to monitor and analyze industrial process data from DCS/SCADA systems via MCP protocol, with domain expert knowledge for anomaly detection and recommendations.

Enables an AI assistant to diagnose a broken application on a local Kubernetes cluster by inspecting pods, events, and logs, with server-side guardrails, least-privilege RBAC, and an audit log. It can also restart deployments in allowed namespaces only after a dry-run preview and host approval.

A live post-mortem debugger MCP server for Home Assistant that lets AI agents list captured exceptions, walk traceback frames, read local variables, and optionally evaluate Python in the context of a captured frame for true post-mortem debugging.

Enables troubleshooting of LDAP directory services through natural language queries, providing health diagnostics, replication status, performance metrics, log analysis, and configuration comparisons across multiple servers.

An MCP server that exposes Home Assistant's REST and WebSocket APIs as 182 tools, enabling clients like Claude Code to control lights, climate, media, automations, and more. It also provides a status dashboard and supports running as a Home Assistant app or container.

Enables LLMs to query real job data and summarize backend job failures using MCP tools backed by a SQLite database.

MCP server that connects LLMs to Kubernetes clusters for troubleshooting, scanning failing pods, diagnosing root causes, and applying guarded fixes or generating manifests via natural language.

Monitor website health, uptime, SEO, security and performance via your AI assistant.

Enables read-only system diagnostics on approved Linux hosts over SSH, with allowlisted commands, bounded output, and secure log access.

Provides comprehensive logging and monitoring capabilities for MCP services with real-time log tailing, advanced search, error analysis, and anomaly detection. Enables centralized log aggregation, correlation tracking, and health monitoring across all MCP ecosystem services.

A Model Context Protocol (MCP) server that lets an AI assistant read and operate the Lumics network monitoring platform via its REST API.

Lets an AI assistant answer performance questions from Tideways data by reading projects, metrics, issues and traces through the read-only REST API.

MCP server for the beacon log analytics platform, exposing beacon's REST API as MCP tools and resources for AI agents to query and analyse AI-assistant usage data.

Provides structured access to Claude Code agent log files, allowing agents to query assistant lines and tool calls without reading raw JSONL data.

A Model Context Protocol server for the AVEQ Surfmeter management API. It exposes typed tools for clients, measurements, anomalies, groups, ISPs, users, keys, capabilities, settings, license usage, and the built-in AI assistant.

Lets your coding agent talk to the RunWhen platform — workspace chat, issues, SLXs, run sessions, and the Tool Builder — over the Model Context Protocol. Enables workspace chat with AI assistant, task authoring via Tool Builder, and direct data access to workspaces, issues, SLXs, run sessions, and more.

Lets an assistant read recorded production AI agent runs — steps, model and tool calls with arguments, and outcomes — along with the findings of comparison runs that checked a prompt or model change against those recordings, and verify a signed evidence bundle offline with no account or network. It is strictly read-only: no tool starts a replay or comparison, so nothing can spend money or act without a person deciding.

Lets an AI assistant inspect a running Google Chrome or Microsoft Edge browser over the Chrome DevTools Protocol, reading console output, network traffic, DOM snapshots, errors, performance metrics, storage, and screenshots. It also supports live event subscriptions, screen-frame streaming, and one-shot export of everything into an offline-readable archive such as HAR, CSV, and a self-contained HTML report.