Skip to main content
Glama

Hass-MCP

Un servidor de Protocolo de Contexto de Modelo (MCP) para la integración de Home Assistant con Claude y otros LLM.

Descripción general

Hass-MCP permite que los asistentes de IA como Claude interactúen directamente con su instancia de Home Assistant, lo que les permite:

  • Consultar el estado de dispositivos y sensores

  • Controlar luces, interruptores y otras entidades

  • Obtenga resúmenes de su hogar inteligente

  • Solucionar problemas de automatizaciones y entidades

  • Buscar entidades específicas

  • Crear conversaciones guiadas para tareas comunes

Related MCP server: Home Assistant MCP Server

Capturas de pantalla

Características

  • Gestión de entidades : obtener estados, controlar dispositivos y buscar entidades

  • Resúmenes de dominio : obtenga información de alto nivel sobre los tipos de entidad

  • Soporte de automatización : enumerar y controlar automatizaciones

  • Conversaciones guiadas : utilice indicaciones para tareas comunes, como la creación de automatizaciones.

  • Búsqueda inteligente : busque entidades por nombre, tipo o estado

  • Eficiencia de tokens : respuestas JSON optimizadas para minimizar el uso de tokens

Instalación

Prerrequisitos

  • Instancia de Home Assistant con token de acceso de larga duración

  • Uno de los siguientes:

    • Docker (recomendado)

    • Python 3.13+ y uv

Configuración con Claude Desktop

Instalación de Docker (recomendada)

  1. Extraiga la imagen de Docker:

    docker pull voska/hass-mcp:latest
  2. Agregue el servidor MCP a Claude Desktop:

    a. Abra Claude Desktop y vaya a Configuración. b. Vaya a Desarrollador > Editar configuración. c. Agregue la siguiente configuración a su archivo claude_desktop_config.json :

    {
      "mcpServers": {
        "hass-mcp": {
          "command": "docker",
          "args": [
            "run",
            "-i",
            "--rm",
            "-e",
            "HA_URL",
            "-e",
            "HA_TOKEN",
            "voska/hass-mcp"
          ],
          "env": {
            "HA_URL": "http://homeassistant.local:8123",
            "HA_TOKEN": "YOUR_LONG_LIVED_TOKEN"
          }
        }
      }
    }

    d. Reemplace YOUR_LONG_LIVED_TOKEN con su token de acceso de larga duración de Home Assistant. e. Actualice HA_URL :

    • Si ejecuta Home Assistant en la misma máquina: use http://host.docker.internal:8123 (Docker Desktop en Mac/Windows)

    • Si ejecuta Home Assistant en otra máquina: use la IP o el nombre de host real

    f. Guarde el archivo y reinicie Claude Desktop.

  3. La herramienta "Hass-MCP" ahora debería aparecer en el menú de herramientas de Claude Desktop.

Nota : Si ejecuta Home Assistant en Docker en la misma máquina, es posible que deba agregar --network host a los argumentos de Docker para que el contenedor acceda a Home Assistant. Como alternativa, use la dirección IP de su máquina en lugar de host.docker.internal .

Otros clientes de MCP

Cursor

  1. Vaya a Configuración del cursor > MCP > Agregar nuevo servidor MCP

  2. Rellene el formulario:

    • Nombre: Hass-MCP

    • Tipo: command

    • Dominio:

      docker run -i --rm -e HA_URL=http://homeassistant.local:8123 -e HA_TOKEN=YOUR_LONG_LIVED_TOKEN voska/hass-mcp
    • Reemplace YOUR_LONG_LIVED_TOKEN con su token de Home Assistant real

    • Actualice HA_URL para que coincida con la dirección de su instancia de Home Assistant

  3. Haga clic en "Agregar" para guardar

Código Claude (CLI)

Para usar con Claude Code CLI, puede agregar el servidor MCP directamente usando el comando mcp add :

Usando Docker (recomendado):

claude mcp add hass-mcp -e HA_URL=http://homeassistant.local:8123 -e HA_TOKEN=YOUR_LONG_LIVED_TOKEN -- docker run -i --rm -e HA_URL -e HA_TOKEN voska/hass-mcp

Reemplace YOUR_LONG_LIVED_TOKEN con su token de Home Assistant real y actualice HA_URL para que coincida con la dirección de su instancia de Home Assistant.

Ejemplos de uso

A continuación se muestran algunos ejemplos de indicaciones que puede utilizar con Claude una vez configurado Hass-MCP:

  • "¿Cuál es el estado actual de las luces de mi sala de estar?"

  • "Apaga todas las luces de la cocina"

  • "Enumerar todos mis sensores que contienen datos de temperatura"

  • "Dame un resumen de mis entidades climáticas"

  • "Crea una automatización que encienda las luces al atardecer"

  • "Ayúdenme a solucionar el problema de por qué el sensor de movimiento de mi habitación no funciona"

  • "Buscar entidades relacionadas con mi sala de estar"

Herramientas disponibles

Hass-MCP proporciona varias herramientas para interactuar con Home Assistant:

  • get_version : Obtener la versión de Home Assistant

  • get_entity : obtiene el estado de una entidad específica con filtrado de campo opcional

  • entity_action : Realizar acciones sobre las entidades (activar, desactivar, alternar)

  • list_entities : obtiene una lista de entidades con filtrado de dominio y búsqueda opcionales

  • search_entities_tool : busca entidades que coincidan con una consulta

  • domain_summary_tool : Obtener un resumen de las entidades de un dominio

  • list_automations : Obtener una lista de todas las automatizaciones

  • call_service_tool : Llama a cualquier servicio de Home Assistant

  • restart_ha : Reiniciar Home Assistant

  • get_history : Obtener el historial de estado de una entidad

  • get_error_log : Obtener el registro de errores de Home Assistant

Indicaciones para conversaciones guiadas

Hass-MCP incluye varias indicaciones para conversaciones guiadas:

  • create_automation : Guía para crear automatizaciones de Home Assistant según el tipo de activador

  • debug_automation : Ayuda para la resolución de problemas de automatizaciones que no funcionan

  • troubleshoot_entity : diagnosticar problemas con entidades

  • routine_optimizer : analiza patrones de uso y sugiere rutinas optimizadas según el comportamiento real

  • automation_health_check : Revisar todas las automatizaciones, encontrar conflictos, redundancias u oportunidades de mejora

  • entity_naming_consistency : audita los nombres de las entidades y sugiere mejoras de estandarización

  • dashboard_layout_generator : Crea paneles optimizados según las preferencias del usuario y los patrones de uso

Recursos disponibles

Hass-MCP proporciona los siguientes puntos finales de recursos:

  • hass://entities/{entity_id} : Obtener el estado de una entidad específica

  • hass://entities/{entity_id}/detailed : Obtenga información detallada sobre una entidad con todos los atributos

  • hass://entities : enumera todas las entidades de Home Assistant agrupadas por dominio

  • hass://entities/domain/{domain} : Obtener una lista de entidades para un dominio específico

  • hass://search/{query}/{limit} : busca entidades que coincidan con una consulta con un límite de resultados personalizado

Desarrollo

Ejecución de pruebas

uv run pytest tests/

Licencia

Licencia MIT

Available Tools

29 tools
add_cardA

Add a card to a dashboard view (live)

Args: url_path: Dashboard URL path, or None for the default dashboard. view: Target view — an integer index, or a string matching the view's path or title. card: The card config dict (must include a string type), e.g. {"type": "markdown", "content": "Hello"}. position: Insert index within the target card list (default: append). section: For a "sections"-type view, which section to add into — an index, section title, or heading text. REQUIRED for sections views (use list_view_sections to see them); omit for classic views. dry_run: Preview without saving.

Returns: Save result with a backup_id, or a dry-run preview.

Inputs: card, view, dry_run, section, +2 more. Returns: result

add_viewA

Add a new view to a dashboard (live)

Args: url_path: Dashboard URL path, or None for the default dashboard. view_config: The view config dict, e.g. {"title": "Garage", "path": "garage"}. position: Insert index among views (default: append). dry_run: Preview without saving.

Returns: Save result with a backup_id, or a dry-run preview.

Inputs: dry_run, position, url_path, view_config. Returns: result

call_service_toolA

Call any Home Assistant service (low-level API access)

Args: domain: The domain of the service (e.g., 'light', 'switch', 'automation') service: The service to call (e.g., 'turn_on', 'turn_off', 'toggle') data: Optional data to pass to the service (e.g., {'entity_id': 'light.living_room'})

Returns: A dictionary with success status, the domain/service called, and the list of affected entity states returned by Home Assistant.

Examples: domain='light', service='turn_on', data={'entity_id': 'light.x', 'brightness': 255} domain='automation', service='reload' domain='fan', service='set_percentage', data={'entity_id': 'fan.x', 'percentage': 50}

Inputs: domain (required), service (required), data. Returns: result

domain_summary_toolA

Get a summary of entities in a specific domain

Args: domain: The domain to summarize (e.g., 'light', 'switch', 'sensor') example_limit: Maximum number of examples to include for each state

Returns: A dictionary containing: - total_count: Number of entities in the domain - state_distribution: Count of entities in each state - examples: Sample entities for each state - common_attributes: Most frequently occurring attributes

Examples: domain="light" - get light summary domain="climate", example_limit=5 - climate summary with more examples Best Practices: - Use this before retrieving all entities in a domain to understand what's available

Inputs: domain (required), example_limit. Returns: result

entity_actionA

Perform an action on a Home Assistant entity (on, off, toggle)

Args: entity_id: The entity ID to control (e.g. 'light.living_room') action: The action to perform ('on', 'off', 'toggle') params: Optional dictionary of additional parameters for the service call

Returns: The response from Home Assistant

Examples: entity_id="light.living_room", action="on", params={"brightness": 255} entity_id="switch.garden_lights", action="off" entity_id="climate.living_room", action="on", params={"temperature": 22.5}

Domain-Specific Parameters: - Lights: brightness (0-255), color_temp, rgb_color, transition, effect - Covers: position (0-100), tilt_position - Climate: temperature, target_temp_high, target_temp_low, hvac_mode - Media players: source, volume_level (0-1)

Inputs: action (required), entity_id (required), params.

get_dashboard_configA

Get a dashboard's full configuration

Args: url_path: The dashboard's URL path (e.g. "my-dash"). Omit or pass None for the default "Overview" dashboard.

Returns: The dashboard config dict (a top-level views list of cards). If the dashboard has no stored config yet, returns an empty {"views": []} scaffold with a note.

Inputs: url_path. Returns: result

get_entities_by_areaA

Get all entities assigned to a specific Home Assistant area (room).

Area lookup is case-insensitive and matches the area's name as configured in Home Assistant (e.g., "Kitchen", "Living Room"). Entities inherit their area from their parent device when no area is set directly, matching HA's own resolution behavior.

Args: area: Name of the area to filter by (case-insensitive) domain: Optional domain to further filter results (e.g., 'light') lean: If True (default), returns token-efficient entity records

Returns: A dictionary containing: - area: The matched area name (as canonicalized by HA) - count: Number of matching entities - entities: List of entity records with their state and area

Examples: get_entities_by_area(area="Kitchen") - everything in the kitchen get_entities_by_area(area="Living Room", domain="light") - lights only

Inputs: area (required), lean, domain. Returns: result

get_entityA

Get the state of a Home Assistant entity with optional field filtering

Args: entity_id: The entity ID to get (e.g. 'light.living_room') fields: Optional list of fields to include (e.g. ['state', 'attr.brightness']) detailed: If True, returns all entity fields without filtering

Examples: entity_id="light.living_room" - basic state check entity_id="light.living_room", fields=["state", "attr.brightness"] - specific fields entity_id="light.living_room", detailed=True - all details

Inputs: entity_id (required), fields, detailed.

get_error_logA

Get the Home Assistant error log for troubleshooting.

All filters are optional and combine (AND semantics). Stats (error_count, warning_count, integration_mentions, total_lines) are computed over the filtered output so they match what's returned.

Args: level: Filter to lines containing this log level — ERROR, WARNING, INFO, or DEBUG. Case-insensitive. integration: Filter to lines mentioning this integration. Matches [name] or [homeassistant.components.name]. Case-insensitive. search_term: Case-insensitive substring filter applied per line. Useful for entity IDs, exception names, etc. lines: Return only the most recent N lines (applied after other filters). Useful when you only care about the tail.

Returns: A dictionary containing: - log_text: The (possibly filtered) error log text - error_count: Number of ERROR entries in the filtered output - warning_count: Number of WARNING entries in the filtered output - integration_mentions: Map of integration names to mention counts - total_lines: Number of lines in the filtered output - filters_applied: Map of which filter args were supplied - error: Error message if retrieval failed

Examples: get_error_log() # full log get_error_log(level="ERROR") # errors only get_error_log(integration="zwave_js") # one integration get_error_log(search_term="light.kitchen") # specific entity get_error_log(level="ERROR", lines=50) # last 50 errors

Best Practices: - Filter on the server side (here) rather than pulling the full log into Claude's context — saves tokens on noisy logs. - Combine integration + level="ERROR" to triage a single integration that's misbehaving. - Use lines to bound output when scanning a long-running HA.

Inputs: level, lines, integration, search_term. Returns: result

get_historyA

Get the history of an entity's state changes

Args: entity_id: The entity ID to get history for hours: Number of hours of history to retrieve (default: 24)

Returns: A dictionary containing: - entity_id: The entity ID requested - states: List of state objects with timestamps - count: Number of state changes found - first_changed: Timestamp of earliest state change - last_changed: Timestamp of most recent state change

Examples: entity_id="light.living_room" - get 24h history entity_id="sensor.temperature", hours=168 - get 7 day history Best Practices: - Keep hours reasonable (24-72) for token efficiency - Use for entities with discrete state changes rather than continuously changing sensors - Consider the state distribution rather than every individual state

Inputs: entity_id (required), hours. Returns: result

get_history_rangeA

Get raw state-change history for an entity over a date/time range.

Like get_history, but takes an explicit window instead of "N hours from now". Useful for inspecting what happened on a specific day or correlating with an external event.

Args: entity_id: The entity to fetch history for. start_time: ISO-8601 start (e.g. 2026-05-15 or 2026-05-15T08:00:00Z). Treated as UTC if no offset. end_time: ISO-8601 end. Defaults to now (UTC).

Returns: Same shape as get_history: entity_id, states, count, first_changed, last_changed.

Examples: get_history_range("light.kitchen", "2026-05-15") get_history_range("sensor.power", "2026-05-15T00:00:00Z", "2026-05-16T00:00:00Z")

Best Practices: - Bound the window — wider ranges return more data and more tokens. - For aggregated long-term data, prefer get_statistics_range.

Inputs: entity_id (required), start_time (required), end_time. Returns: result

get_statisticsA

Get long-term aggregated statistics for an entity over the last N hours.

Uses HA's recorder statistics (over WebSocket) — aggregated buckets (mean / min / max per period) that survive the short-term retention window. Use this instead of get_history when: - You want data older than the recorder's default 10-day window. - You want aggregated values rather than every individual change. - The entity is a high-frequency sensor (temperature, power) and raw history would be too many tokens.

Args: entity_id: The entity (must have a state_class HA records as statistics — measurement, total, total_increasing). hours: How far back from now. Defaults to 24. period: Bucket size — 5minute, hour, day, week, month. Defaults to hour.

Returns: entity_id, period, start_time, end_time, statistics (list of {start, end, mean, min, max, ...} points).

Examples: get_statistics("sensor.power_usage", hours=168, period="day") get_statistics("sensor.temperature", hours=24)

Inputs: entity_id (required), hours, period. Returns: result

get_statistics_rangeA

Get long-term aggregated statistics for an entity over a date/time range.

Same data source as get_statistics, but with an explicit window — useful for "what was my power usage from Jan 1 to Jan 31?" type questions. Aggregated bucket data survives the short-term retention window, so this works for data months/years old.

Args: entity_id: The entity (must be statistics-tracked). start_time: ISO-8601 start (2026-01-01 or 2026-01-01T00:00:00Z). UTC if no offset. end_time: ISO-8601 end. Defaults to now. period: 5minute, hour, day, week, or month.

Returns: entity_id, period, start_time, end_time, statistics.

Examples: get_statistics_range("sensor.energy", "2026-01-01", "2026-02-01", period="day") get_statistics_range("sensor.temperature", "2026-05-01", period="hour")

Inputs: entity_id (required), start_time (required), period, end_time. Returns: result

get_versionA

Get the Home Assistant version

Returns: A string with the Home Assistant version (e.g., "2025.3.0")

Inputs: no named parameters. Returns: result

list_automationsA

Get a list of all automations from Home Assistant

This function retrieves all automations configured in Home Assistant, including their IDs, entity IDs, state, and display names.

Returns: A list of automation dictionaries, each containing id, entity_id, state, and alias (friendly name) fields.

Examples: Returns all automation objects with state and friendly names

Inputs: no named parameters. Returns: result

list_dashboard_backupsA

List on-disk backups of a dashboard's config

Backups are written automatically before every dashboard write. NOTE: in Docker, backups persist only if HASS_MCP_BACKUP_DIR is volume-mounted.

Args: url_path: Dashboard URL path, or None for the default dashboard.

Returns: A list of {backup_id, path}, oldest first.

Inputs: url_path. Returns: result

list_dashboardsA

List Home Assistant dashboards (Lovelace)

Returns: A list of dashboards. Each entry has url_path (None for the default "Overview" dashboard), title, and mode ("storage" or "yaml"). Only "storage"-mode dashboards can be edited via these tools.

Inputs: no named parameters. Returns: result

list_entitiesA

Get a list of Home Assistant entities with optional filtering

Args: domain: Optional domain to filter by (e.g., 'light', 'switch', 'sensor') search_query: Optional search term to filter entities by name, id, or attributes (Note: Does not support wildcards. To get all entities, leave this empty) limit: Maximum number of entities to return (default: 100) fields: Optional list of specific fields to include in each entity detailed: If True, returns all entity fields without filtering

Returns: A list of entity dictionaries with lean formatting by default

Examples: domain="light" - get all lights search_query="kitchen", limit=20 - search entities domain="sensor", detailed=True - full sensor details

Best Practices: - Use lean format (default) for most operations - Prefer domain filtering over no filtering - For domain overviews, use domain_summary_tool instead of list_entities - Only request detailed=True when necessary for full attribute inspection - To get all entity types/domains, use list_entities without a domain filter, then extract domains from entity_ids

Inputs: limit, domain, fields, detailed, +1 more. Returns: result

list_view_sectionsA

List the sections of a "sections"-type dashboard view

Modern Home Assistant views of type: sections hold their cards inside sections (not a top-level card list). Use this to discover which section to target with the card tools' section argument.

Args: url_path: Dashboard URL path, or None for the default dashboard. view: Target view (index, or matching path/title).

Returns: A list of {index, title, heading, card_count}, one per section. Errors if the view is not a sections view.

Inputs: view, url_path. Returns: result

move_cardB

Reorder a card within a dashboard view (live)

Args: url_path: Dashboard URL path, or None for the default dashboard. view: Target view (index, or matching path/title). card_index: Current index of the card. new_index: Destination index within the same card list. section: For a "sections"-type view, which section the card is in (index/title/heading). Required for sections views. dry_run: Preview without saving.

Returns: Save result with a backup_id, or a dry-run preview.

Inputs: view, dry_run, section, url_path, +2 more. Returns: result

remove_cardA

Remove a card from a dashboard view (live)

Args: url_path: Dashboard URL path, or None for the default dashboard. view: Target view (index, or matching path/title). card_index: Index of the card to remove within the target card list. section: For a "sections"-type view, which section the card is in (index/title/heading). Required for sections views. dry_run: Preview without saving.

Returns: Save result with a backup_id, or a dry-run preview.

Inputs: view, dry_run, section, url_path, +1 more. Returns: result

remove_viewA

Remove a view from a dashboard (live)

⚠️ Removes the view and all its cards.

Args: url_path: Dashboard URL path, or None for the default dashboard. view: Target view (index, or matching path/title). dry_run: Preview without saving.

Returns: Save result with a backup_id, or a dry-run preview.

Inputs: view, dry_run, url_path. Returns: result

restart_haA

Restart Home Assistant

⚠️ WARNING: Temporarily disrupts all Home Assistant operations

Returns: Result of restart operation

Inputs: no named parameters. Returns: result

restore_dashboardA

Restore a dashboard from a backup (live)

Restores the most recent backup unless backup_id is given. The current config is itself backed up first, so a restore can be undone.

Args: url_path: Dashboard URL path, or None for the default dashboard. backup_id: A specific backup id from list_dashboard_backups (default: newest). dry_run: Preview without saving.

Returns: Save result plus restored_from, or a dry-run preview.

Inputs: dry_run, url_path, backup_id. Returns: result

search_entities_toolA

Search for entities matching a query string

Args: query: The search query to match against entity IDs, names, and attributes. (Note: Does not support wildcards. To get all entities, leave this blank or use list_entities tool) limit: Maximum number of results to return (default: 20)

Returns: A dictionary containing search results and metadata: - count: Total number of matching entities found - results: List of matching entities with essential information - domains: Map of domains with counts (e.g. {"light": 3, "sensor": 2})

Examples: query="temperature" - find temperature entities query="living room", limit=10 - find living room entities query="", limit=500 - list all entity types

Inputs: query (required), limit. Returns: result

set_dashboard_configA

Replace a dashboard's full configuration (low-level write)

⚠️ WARNING: Overwrites the ENTIRE dashboard and updates every open browser live. The prior config is backed up first (use restore_dashboard to undo). Requires an admin token; only storage-mode dashboards can be saved.

Args: url_path: Dashboard URL path, or None for the default dashboard. config: The complete new config dict (must contain a views list). dry_run: If True, validate and return the resulting config + a change summary WITHOUT saving.

Returns: On save: {success, url_path, backup_id, summary}. On dry_run: {dry_run: True, url_path, summary, config}.

Inputs: config, dry_run, url_path. Returns: result

system_overviewA

Get a comprehensive overview of the entire Home Assistant system

Returns: A dictionary containing: - total_entities: Total count of all entities - domains: Dictionary of domains with their entity counts and state distributions - domain_samples: Representative sample entities for each domain (2-3 per domain) - domain_attributes: Common attributes for each domain - area_distribution: Entities grouped by area (if available)

Examples: Returns domain counts, sample entities, and common attributes Best Practices: - Use this as the first call when exploring an unfamiliar Home Assistant instance - Perfect for building context about the structure of the smart home - After getting an overview, use domain_summary_tool to dig deeper into specific domains

Inputs: no named parameters. Returns: result

update_cardB

Replace a card in a dashboard view (live)

Args: url_path: Dashboard URL path, or None for the default dashboard. view: Target view (index, or matching path/title). card_index: Index of the card to replace within the target card list. card: The new card config dict (must include a string type). section: For a "sections"-type view, which section the card is in (index/title/heading). Required for sections views. dry_run: Preview without saving.

Returns: Save result with a backup_id, or a dry-run preview.

Inputs: card, view, dry_run, section, +2 more. Returns: result

update_viewA

Update a view's properties — title, path, icon, etc. (live)

Cards in the view are preserved unless changes includes a cards key.

Args: url_path: Dashboard URL path, or None for the default dashboard. view: Target view (index, or matching path/title). changes: Dict of view properties to merge in, e.g. {"title": "New Title"}. dry_run: Preview without saving.

Returns: Save result with a backup_id, or a dry-run preview.

Inputs: view, changes, dry_run, url_path. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 29 tools

    Disambiguation3/5

    Most tools target distinct resources, but several overlap: entity_action vs call_service_tool both invoke services (the former is just a convenience wrapper), and list_entities (with its search_query param) vs search_entities_tool both perform entity search. The detailed descriptions cross-reference each other and help steer the agent, but a few genuine selection ambiguities remain.

    Naming Consistency3/5

    The majority follow a clean verb_noun pattern (list_dashboards, add_card, remove_view, get_history, get_statistics). However, three tools carry inconsistent _tool suffixes (domain_summary_tool, search_entities_tool, call_service_tool) and a few use noun-first names (entity_action, system_overview) or bare verbs (restart_ha), breaking the otherwise consistent convention.

    Tool Count2/5

    At 29 tools this is heavy, and 13 of them are dashboard/Lovelace operations (card/view CRUD plus backups) that dominate the surface. While each dashboard operation is distinct, the overall set is well past the comfortable 3-15 range and several card/view tools could arguably be consolidated.

    Completeness4/5

    Coverage for entities, history/statistics, services, dashboards, and system diagnostics is strong end-to-end. Gaps exist around automations (only list_automations, no create/edit/trigger), scripts, scenes, and area listing, but call_service_tool provides a general escape hatch so agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      C
      maintenance
      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.
      4
      48
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that integrates with Home Assistant to provide smart home control capabilities through natural language, supporting devices like lights, climate systems, locks, alarms, and humidifiers.
      3
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A self-hosted MCP server for Home Assistant that exposes full control over entity states, service calls, history, templates, and areas via local stdio, enabling AI assistants to manage your smart home.
      9
      108 npm
      MIT