Skip to main content
Glama
FernanMoreno

domoai-mcp

by FernanMoreno

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DOMOAI_MCP_HOSTNoHost address to bind the shared network gateway.
DOMOAI_MCP_PATHNoPath for the shared network gateway.
DOMOAI_MCP_PORTNoPort for the shared network gateway.
DOMOAI_ENERGY_LIVENoSet to 1 to enable live energy data collection.
DOMOAI_MODBUS_HOSTNoHostname of the Modbus TCP controller.
DOMOAI_MODBUS_PORTNoPort of the Modbus TCP controller (default '502').
DOMOAI_DATABASE_PATHNoPath to the SQLite database file.
DOMOAI_MQTT_PASSWORDNoPassword for MQTT broker authentication.
DOMOAI_MQTT_USERNAMENoUsername for MQTT broker authentication.
DOMOAI_MCP_PUBLIC_URLNoPublic URL for the shared network gateway.
DOMOAI_SOLAR_PROVIDERNoSolar forecast provider, e.g., 'open_meteo'.
DOMOAI_KNX_CONFIG_PATHNoPath to the KNX mapping JSON file.
DOMOAI_TARIFF_PROVIDERNoTariff provider, e.g., 'omie'.
DOMOAI_ZIGBEE2MQTT_URLNoMQTT broker URL for Zigbee2MQTT, e.g., 'mqtt://mqtt-broker.local:1883'.
DOMOAI_KNX_GATEWAY_HOSTNoHostname of the KNX/IP gateway.
DOMOAI_MATTER_SERVER_URLNoWebSocket URL of the Matter Server, e.g., 'ws://matter-server.local:5580/ws'.
DOMOAI_HOME_ASSISTANT_URLNoBase URL of the Home Assistant instance. Required with DOMOAI_HOME_ASSISTANT_TOKEN for the live Home Assistant runtime.
DOMOAI_MODBUS_CONFIG_PATHNoPath to the Modbus mapping JSON file.
DOMOAI_SOLAR_PROFILE_PATHNoPath to the solar profile JSON file.
DOMOAI_KNX_TIMEOUT_SECONDSNoTimeout in seconds for KNX operations.
DOMOAI_HOME_ASSISTANT_TOKENNoLong-lived access token for Home Assistant. Required with DOMOAI_HOME_ASSISTANT_URL.
DOMOAI_MQTT_TIMEOUT_SECONDSNoTimeout in seconds for MQTT operations.
DOMOAI_MCP_CLIENT_TOKEN_FILENoPath to a file containing the bearer token. Required when binding to a non-loopback address.
DOMOAI_MATTER_TIMEOUT_SECONDSNoTimeout in seconds for Matter Server operations.
DOMOAI_MODBUS_TIMEOUT_SECONDSNoTimeout in seconds for Modbus operations.
DOMOAI_ZIGBEE2MQTT_BASE_TOPICNoBase MQTT topic for Zigbee2MQTT (default 'zigbee2mqtt').
DOMOAI_BATTERY_HIL_EVIDENCE_PATHNoPath to hardware-in-the-loop evidence file required for production battery dispatch.
DOMOAI_BATTERY_DISPATCH_PRODUCTIONNoSet to 1 to enable production battery dispatch. Requires matching HIL evidence.
DOMOAI_HOME_ASSISTANT_MAPPING_PATHNoPath to a Home Assistant metric mapping JSON file.
DOMOAI_MODBUS_POLL_INTERVAL_SECONDSNoPolling interval in seconds for Modbus data collection.
DOMOAI_BATTERY_DISPATCH_PROFILE_PATHNoPath to the dispatchable battery profile JSON file.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
discover_devicesB

Read or refresh the canonical semantic device inventory.

inspect_commissioningA

Read the shared, non-authoritative commissioning report for future battery and EV bindings.

get_stateC

Read bounded semantic state snapshots for selected devices.

get_energy_contextB

Read a complete canonical energy context for one requested horizon.

validate_commandB

Validate one semantic command without invoking an adapter.

validate_planC

Validate a semantic plan and return its policy decisions and digest.

request_approvalA

Issue a server-authoritative approval grant for a plan requiring confirmation. A trusted host may inject an authenticated operator principal. The optional operator_token exists only for explicitly enabled local/dev compatibility mode; the caller never supplies the recorded operator identity. The returned approval_id is single-use and bound to the plan's current validation digest.

execute_planB

Execute a previously validated plan after runtime safety checks.

schedule_planA

Schedule a previously validated/approved plan to execute at a future time, instead of immediately. The plan still goes through every existing safety check when its time arrives.

commit_or_schedule_bundleC

Commit one validated bundle through the runtime-owned physical execution and scheduling boundary.

cancel_scheduled_planA

Cancel a pending scheduled plan before it executes.

reschedule_planA

Request a temporal revision for a pending plan. The legacy generic mutation is fail-closed; a changed time must be validated and approved again before admission.

list_scheduled_plansA

List plans currently pending their scheduled execution time.

schedule_recurring_planA

Schedule a plan's commands to run repeatedly at a fixed local time, optionally restricted to specific weekdays. Creating a standing automation is its own authority act, distinct from running the commands once: if the template plan currently requires confirmation, an approval_id from request_approval is required to create the schedule at all. Every occurrence is still independently revalidated against live state before it executes; an occurrence requiring confirmation at run time is skipped and audited, never auto-approved, and recurrence continues to its next scheduled time. An optional expires_at bounds how long the automation stays active.

cancel_recurring_scheduleB

Cancel a recurring schedule; stops all future occurrences.

list_recurring_schedulesA

List active recurring schedules and their next occurrence.

list_audit_eventsA

Query the bounded, filterable audit trail of runtime decisions.

validate_scenarioB

Validate an optimization scenario against canonical devices and capabilities.

optimize_scenarioA

Compute a deterministic proposal without executing physical commands.

explain_solutionA

Explain a typed optimization result without changing runtime state.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
areas_resource
capabilities_resource
devices_resource
energy_resource
policies_resource
metrics_resource
runtime_resource
commissioning_resource

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FernanMoreno/DomoAI'

If you have feedback or need assistance with the MCP directory API, please join our Discord server