Mcp Superassistant Proxy Unified

Showing 25 of 87 from the live probe.

• Get Apps (add-ons)

  Get installed or available Home Assistant apps (add-ons), or details for one. Do not use this tool to change app state or configuration; use ``ha_manage_app``. Use ``slug`` for details, ``source="installed"`` for an inventory, or ``source="available"`` for store discovery. Requires Home Assistant OS or Supervised. ``include_stats`` applies only to installed-app listings.

• Manage App (add-on)

  Manage Home Assistant apps (add-ons) or proxy an app API. For app inventory, status, and Supervisor metadata, call ``ha_get_app`` first; use proxy mode here for documented app-specific read APIs. Do not infer private app API schemas; consult version-matched app docs, and use ``ha_get_skill_guide`` for complex Home Assistant workflows. Use exactly one mode: lifecycle/store action, configuration fields, ``path`` proxy, or ``path`` with ``array_patch``. Requires Home Assistant OS or Supervised.

• List Floors and Areas

  List floors sorted by level ascending, each with their assigned areas nested, plus areas without a floor. Use for location-based reasoning where floor-to-area relationships matter, such as "which rooms are on the ground floor" or operations scoped to a level. Optionally project the response with fields= (top-level keys) or area_fields= (per-area-record keys, applied uniformly across nested, unassigned, and orphaned buckets). Floors with level=None sort alongside level 0 (ground floor). Areas w

• Remove Area or Floor

  Remove a Home Assistant area or floor. Removing an area unassigns its entities and devices (the entities and devices themselves are not removed). Removing a floor unassigns its areas. May break automations referencing the removed area/floor.

• Create or Update Area or Floor

  Create or update a Home Assistant area or floor. Pass kind='area' (with optional floor_id, picture) or kind='floor' (with optional level). Provide name only to create a new entry; provide id to update an existing one. Cross-kind parameters (e.g., picture under kind='floor') are rejected with VALIDATION_INVALID_PARAMETER. EXAMPLES: ha_set_area_or_floor(kind="area", name="Kitchen") ha_set_area_or_floor(kind="area", id="kitchen", floor_id="ground_floor") ha_set_area_or_floor(kind="floor", name="B

• Manage Assist Pipeline

  Manage Home Assistant Assist pipelines. Use action='list' to discover pipeline IDs, action='get' to inspect one pipeline, action='create' or action='update' to write pipeline settings, action='set_preferred' to choose the preferred pipeline, and action='process' to run a sentence through Assist. action='process' sends the sentence straight to Assist's conversation agent, so a matched intent executes: it turns on the light rather than reporting that it would. Its result carries response_type ('

• Manage Blueprints

  Manage Home Assistant blueprints — list, read, import, save, delete, or render a standalone config. One interface for the whole blueprint lifecycle in the ``automation`` and ``script`` domains. DO NOT use this to create an automation or script FROM a blueprint — that is ``ha_config_set_automation`` / ``ha_config_set_script`` with a ``use_blueprint`` config. Use ``action="list"`` to discover installed blueprints, ``action="get"`` for one blueprint's metadata, inputs and YAML, ``action="import"

• Report Issue or Feedback

  Get diagnostic information plus a ready-to-file report template. Covers two kinds of report: a runtime bug (ha-mcp errored or behaved unexpectedly) and agent-behaviour feedback (the AI used the wrong tool or worked inefficiently). Pick based on whether the fault was in ha-mcp or in the agent's own choices. The response carries the full workflow in its `instructions` field — duplicate check, template selection, the mandatory anonymisation step, and the submit URLs — plus `missing_tool_hint` for

• Get Calendar Events

  Retrieve calendar events from a calendar entity. Retrieves calendar events within a specified time range. **Parameters:** - entity_id: Calendar entity ID (e.g., 'calendar.family') - start: Start datetime in ISO format (default: now) - end: End datetime in ISO format (default: 7 days from start) - max_results: Maximum number of events to return (default: 20) **Example Usage:** ```python # Get events for the next week events = ha_config_get_calendar_events("calendar.family") # Get events for a

• Remove Calendar Event

  Delete an event from a calendar. Deletes a calendar event via the WebSocket ``calendar/event/delete`` command. HA's calendar component only registers ``create_event`` and ``get_events`` as REST services — delete and update live on the WebSocket API only. **Parameters:** - entity_id: Calendar entity ID (e.g., 'calendar.family') - uid: Unique identifier of the event to delete - recurrence_id: Optional recurrence ID for recurring events - recurrence_range: Optional recurrence range ('THIS_AND_FUT

• Create or Update Calendar Event

  Create a new event in a calendar. Creates a one-off event via the calendar.create_event service, or a recurring series via the WebSocket ``calendar/event/create`` command when ``rrule`` is provided (the REST service schema does not accept recurrence rules). **When NOT to use:** - To retrieve calendar events, use ``ha_config_get_calendar_events``. - To delete an event, use ``ha_config_remove_calendar_event``. **Example Usage:** ```python # Create a simple event result = ha_config_set_calendar_

• Get Camera Image

  Retrieve a snapshot image from a Home Assistant camera entity. This tool fetches the current camera image and returns it directly for visual analysis. Use this when you need to see what a camera is currently viewing. **Parameters:** - entity_id: Camera entity ID (e.g., 'camera.front_door', 'camera.living_room') - width: Optional width to resize the image (reduces token usage for large images) - height: Optional height to resize the image **Use Cases:** - Security checks: "Is someone at the fr

• Get Category

  Get category info - list all categories for a scope or get a specific one by ID. Without a category_id: Lists all Home Assistant categories for the given scope. With a category_id: Returns configuration for that specific category. Categories are domain-scoped organizational groups for automations, scripts, scenes, and helpers. CATEGORY PROPERTIES: - ID (category_id), Name - Icon (optional) EXAMPLES: - List automation categories: ha_config_get_category("automation") - List script categories:

• Remove Category

  Delete a Home Assistant category. Removes the category from the category registry for the given scope (e.g., 'automation', 'script', 'scene', 'helpers'). This will also remove the category assignment from all entities in that scope. EXAMPLES: - Delete category: ha_config_remove_category("automation", "my_category_id") Use ha_config_get_category() to find category IDs. **WARNING:** Deleting a category will remove it from all assigned entities. This action cannot be undone.

• Create or Update Category

  Create or update a Home Assistant category. Creates a new category if category_id is not provided, or updates an existing category if category_id is provided. Categories are domain-scoped organizational groups for automations, scripts, scenes, and helpers. Unlike labels (which are cross-domain), categories are specific to a single domain scope. EXAMPLES: - Create automation category: ha_config_set_category("Lighting", scope="automation") - Create with icon: ha_config_set_category("Security",

• Custom Tool

  Create and run a custom tool in a sandbox, or manage saved custom tools. ⚠️ **LAST RESORT** — search for existing tools first. **Modes** (mutually exclusive): - Provide ``code`` + ``justification`` to execute custom code - Set ``run_saved`` to re-run a previously saved tool by name - Set ``list_saved=True`` to list all saved tools **Available functions in sandbox:** - ``api_get(endpoint)`` — GET request to HA REST API - ``api_post(endpoint, data)`` — POST request to HA REST API - ``ws_send(m

• Get Automation Config

  Get a Home Assistant automation configuration by entity_id or unique_id. Returns the full config (trigger, condition, action, mode) plus a stable config_hash for use with python_transform on ha_config_set_automation. For schema and field-level details, see ha_get_skill_guide. read inspect fetch view existing automation config triggers conditions actions get show detail

• Remove Automation

  Delete a Home Assistant automation. The returned `automation_id` is the resolved entity_id (canonical form, e.g. `automation.morning_routine`) when the registry lookup succeeded before the delete, falling back to the input `identifier` otherwise. EXAMPLES: - Delete automation: ha_config_remove_automation("automation.old_automation") - Delete by unique_id: ha_config_remove_automation("my_unique_id") **WARNING:** Deleting an automation removes it permanently from your Home Assistant configurati

• Create or Update Automation

  Create or update a Home Assistant automation. Supports three modes: full `config` replacement, surgical `python_transform` on an existing automation (requires `identifier` and `config_hash` from ha_config_get_automation), or `take_control_of_blueprint` to convert a blueprint-backed automation into an editable standalone one (the UI's Take control action). Omit `identifier` to create a new automation. Reusing an identifier targets the same automation; changing its alias requires config_hash from

• Delete Dashboard

  Delete a storage-mode dashboard completely. WARNING: This permanently deletes the dashboard and all its configuration. Cannot be undone. Does not work on YAML-mode dashboards. Accepts either the URL path or the internal dashboard ID. HA internal IDs may differ from url_path (e.g. hyphens → underscores); the tool resolves either form to the actual registry ID before deletion. EXAMPLES: - Delete dashboard: ha_config_delete_dashboard("mobile-dashboard") Note: The default dashboard cannot be del

• Get Dashboard

  Get Home Assistant dashboard info (list mode, search mode, or full config). Three modes: (1) list — `list_only=True` returns all storage-mode dashboards with metadata. (2) search — pass any of `entity_id`, `card_type`, `heading` to find cards (including nested ones, with a `python_path`) inside a specific dashboard; the result includes a `config_hash` you can pair with ha_config_set_dashboard(python_transform=...) to edit matched cards surgically. (3) get — no search params returns the full Lov

• Create or Update Dashboard

  Create or update a Home Assistant dashboard. Three modes: full `config` replacement for new dashboards or restructures; `patch` for known JSON Pointer paths with literal values (add/remove/replace/test, up to 100 operations; use `-` to append to arrays); `python_transform` for loops and pattern-based edits. Both edit modes require `config_hash` from ha_config_get_dashboard. Choose one mode for content changes; omit all three for metadata-only calls. With patch, change sidebar metadata in a sepa

• List Helpers

  List Home Assistant helpers of a given type, one page per call (`limit`/`offset`; `total_count` and `has_more` describe the full set). The 12 storage-backed types (input_button, input_boolean, input_select, input_number, input_text, input_datetime, counter, timer, schedule, zone, person, tag) are listed on every install. Flow-based types (template, group, utility_meter, derivative, and the rest) and `helper_type='all'` are served only through the ha_mcp_tools custom component. For per-type sche

• Create or Update Helper

  Create or update a Home Assistant helper. Supports all supported helper types: the simple types (input_*, counter, timer, schedule, zone, person, tag) and the flow-based types (template, group, utility_meter, derivative, statistics, trend, threshold, filter, switch_as_x, and others). Field set is delivered as `data_schema` on the first validation error — submit once and self-correct. For decision matrix and worked examples (which helper type for which use case), see ha_get_skill_guide or your l

• Get Scene Config

  Get a Home Assistant scene configuration by scene_id or entity_id. Returns the full config plus a stable config_hash for use with python_transform on ha_config_set_scene. For schema details, see ha_get_skill_guide.