"A device or tool to control Home Assistant" matching MCP servers:

Expose all Home Assistant voice intents through a Model Context Protocol Server allowing home control.

A Model Context Protocol server that allows large language models to control and query Home Assistant smart home systems through natural language interactions.

Provides tools for AI assistants to interact with smart home devices through Home Assistant, allowing operations like checking entity states and calling services.

A server that enables control of smart home devices through the Jenius AI agent system, connecting to Home Assistant to manage devices like Xiaomi air purifiers and smart speakers.

A server that enables interaction with Home Assistant devices and automations through the Model Context Protocol, allowing users to monitor device states, control devices, trigger automations, and list entities.

Enables AI agents to control and monitor Home Assistant smart home devices through natural language interactions. Supports device control, entity state monitoring, history access, and automation generation with both MCP protocol and standalone HTTP REST API modes.

Enables AI agents to control existing Chrome and Firefox browser sessions locally, including tab management, navigation, form filling, screenshots, and persistent scripts, without remote relays or debugging ports.

MCP server that routes natural language requests to structured tool calls using a LoRA-tuned small language model, with built-in validation, retry, and fallback recovery.

A Home Assistant Custom Component that provides an MCP server using HTTP transport, allowing AI assistants like Claude to interact with your Home Assistant instance.

Enables users to deploy a production-grade control plane for agents, providing a spec-compliant MCP server, scoped tool grants, failure-mode detection, and cost governance.

A native MCP server that gives AI assistants full Chrome control via the DevTools Protocol and an unpacked extension, including semantic element refs, real input, screenshots, and browser/tab/window management. It exposes 43 callable tools with a visible control overlay and an optional read-only security profile.

Open-source, Windows-first control plane for operating local and homelab services through typed MCP servers, featuring 13 servers and 290 tools with infrastructure adapters for Windows, Ubuntu, Docker, and more.

An MCP server paired with a Firefox extension that enables LLM clients to control the user's browser, supporting tab management, history search, and content reading.

A dynamic MCP server that hot-reloads tools at runtime and provides URL tracking, onboarding, and scouting features for AI clients.

Enables one coding agent to inspect, configure, debug, and repair another agent over stdio MCP, with redacted reads and confirm-gated writes and restarts.

An MCP proxy that embeds tool definitions and returns only the top-k semantically relevant tools per query, reducing context usage and routing calls to upstream MCP servers.

Central registry for AI tools with vector search and knowledge graph, enabling intelligent tool discovery, chaining, and execution via MCP.

Start, observe, and interact with Claude Managed Agents from any MCP client — launch an agent, watch its events, reply, approve the tools it wants to run, and stop it. Runs over stdio, HTTP, or AWS Lambda with pluggable auth.

Graph-based tool retrieval for LLM agents. Builds a tool graph from OpenAPI/MCP specs and retrieves multi-step workflows via hybrid search (BM25 + graph traversal + embedding), recovering accuracy from 12% to 82% with 79% fewer tokens. Also works as an MCP Proxy to aggregate multiple servers behind 3 meta-tools.

Reliable Codex Desktop automation for long tasks with durable async operations, Plan Mode workflows, and retry-safe task submission.