blueprints_delete_blueprint
Remove an installed Home Assistant blueprint by specifying its relative path, such as 'author/blueprint_name.yaml'.
Instructions
Delete an installed blueprint by its relative path (e.g. 'author/blueprint_name.yaml').
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| domain | No | automation |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Implementation Reference
- tools/blueprints.py:19-22 (handler)The actual handler function for the 'blueprints_delete_blueprint' tool. It calls the Home Assistant WebSocket API with message type 'blueprint/delete', passing a domain and path.
@mcp.tool() def delete_blueprint(path: str, domain: str = "automation") -> dict: """Delete an installed blueprint by its relative path (e.g. 'author/blueprint_name.yaml').""" return ha._ws_call("blueprint/delete", domain=domain, path=path) - ha_client.py:59-66 (helper)The helper function that sends the WebSocket call to Home Assistant. This is the underlying transport used by delete_blueprint.
def _ws_call(msg_type: str, **kwargs) -> Any: try: asyncio.get_running_loop() except RuntimeError: return asyncio.run(_ws_call_async(msg_type, **kwargs)) import concurrent.futures with concurrent.futures.ThreadPoolExecutor() as pool: return pool.submit(asyncio.run, _ws_call_async(msg_type, **kwargs)).result() - server.py:42-42 (registration)Registration of the blueprints MCP server under the 'blueprints' namespace. Combined with the tool name 'delete_blueprint', this produces the full tool name 'blueprints_delete_blueprint'.
mcp.mount(blueprints_mcp, namespace="blueprints") - tools/blueprints.py:4-4 (registration)The FastMCP instance for the blueprints module, mounted with namespace 'blueprints'. The @mcp.tool() decorator on delete_blueprint registers it under this namespace.
mcp = FastMCP("blueprints")