"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.

Enables Alexa+ to call a curated set of Streamable HTTP tools that bridge voice requests to a persistent personal AI agent for asynchronous tasks, memory, home control, calendar, GitHub, and messaging.

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.

MCP router that fronts your other MCP servers behind a few small generic tools, so their tool definitions stay out of the context window and are discovered on demand.

Lets any number of concurrent Claude Code sessions drive a Firefox browser through the Browser Control extension by funneling every session's commands over a single shared port via a background daemon and private unix socket. Sessions no longer have to compete for a limited pool of extension ports, and requests stay isolated through per-request correlation ids.

Enables AI agents to drive a real headful Chrome browser using vision-first computer interactions, with support for multi-agent tab groups, password-manager-filled logins, and human handoff.

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.

Enables LLMs to orchestrate AI agents and tasks, inspect DAG workflows, monitor cluster metrics, and perform safe database queries and statements through standardized MCP tools.

Enables AI coding agents to request a second opinion from a different frontier model via a single tool call, with PII scrubbed before transit, live web search, and support for Claude, ChatGPT, Cursor, and Gemini.

Enables agents to send only the handful of tool definitions relevant to each question, ranking a large catalog by keywords and optional embeddings to cut context cost and wrong-tool picks. It can also run in front of any mcpServers config as a proxy that exposes just search_tools and call_tool instead of the whole catalog.

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.

Enables users to connect a browser workbench to a Streamable HTTP MCP endpoint for natural-language planning, approval-gated tool execution, and simulated home/calendar interactions, with Agent Skills and optional browser speech controls.

Enables AI agents to request an independent second opinion from a different frontier model, with PII scrubbing before transit, live web search grounding, caching, and multi-provider failover.

Enables AI assistants to operate a real, logged-in Firefox session through an extension, including tab and history management, page reading, screenshots, and clicking, typing, or scrolling on domains the user approves.

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.