Fibaro MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIBARO_HOST | No | The hostname or IP address of your Fibaro Home Center | |
| FIBARO_PORT | No | The port number (defaults to 443 for HTTPS, 80 for HTTP) | |
| FIBARO_HTTPS | No | Whether to use HTTPS (defaults to true) | |
| FIBARO_CONFIG | No | Absolute path to a JSON config file containing host, username, password, port, https | |
| FIBARO_TOOLSET | No | Tool listing mode: intent (default), legacy, or both | |
| FIBARO_PASSWORD | No | Your Fibaro password | |
| FIBARO_USERNAME | No | Your Fibaro username |
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
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| first_runA | Setup helper. Use this when configuration is missing. Returns step-by-step instructions plus config templates for common MCP clients. |
| fibaro_deviceA | Device management: list/get/control devices. IMPORTANT: Avoid 'op=list' without filters - it returns 1MB+ of data. Instead: use 'op=get' with 'name' parameter for specific devices, or filter with room_id/type/interface. Supports: turn_on, turn_off, set_brightness, set_color, set_temperature, action, get_lua. |
| fibaro_sceneA | Scene management: list/get/run/stop scenes and Lua code. IMPORTANT: Avoid 'op=list' without filters - use 'op=get' with 'name' or 'id' for specific scenes, or filter by room_id. Supports: run, stop, create, update_lua, get_lua, delete. |
| fibaro_variableC | Variable intent tool: list/get/set/create/delete global variables. |
| fibaro_quick_appB | Quick App intent tool: list/create/update code/update variables/get lua/delete. |
| fibaro_homeB | Home/system management: rooms, sections, users, weather, energy_graph, energy_panel, system_info. For quick stats use 'op=device_stats'. For current power consumption use 'op=energy_panel'. For historical energy/power data use 'op=energy_graph'. Supports: rooms, sections, users, profiles, notifications, alarms, zwave, backups, settings, weather, system_info, energy_graph, energy_panel, plugins. |
| find_by_nameA | Find devices, rooms, or scenes by name (case-insensitive, ignores diacritics). Returns ranked candidates. |
| resolve_by_nameB | Resolve a single device by name (or multiple devices if the query is plural). Errors on ambiguity for singular queries. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Usage Guide | READ THIS FIRST: Efficient tool usage guide to avoid large data transfers |
| Devices | List of all devices in the system (WARNING: 1MB+ - prefer fibaro_device with filters) |
| Rooms | List of all rooms in the system |
| Scenes | List of all scenes in the system (WARNING: large - prefer fibaro_scene with filters) |
| System Info | System information |
| Weather | Current weather information |
| Analytics Dashboard | Comprehensive analytics dashboard with usage patterns, energy trends, and system health |
TDQS
Scored across 8 tools
Most tools target distinct domains (devices, scenes, home, variables, quick apps). However, find_by_name and resolve_by_name overlap significantly in purpose, and fibaro_device also supports name-based retrieval, causing potential confusion.
Five tools follow the 'fibaro_*' prefix convention, but three (find_by_name, first_run, resolve_by_name) break this pattern. Naming is readable but inconsistent, mixing noun phrases with verb phrases.
With 8 tools, the set is well-scoped for a home automation system. Each tool covers a major functional area without being too numerous or sparse.
The tool set covers all major aspects of Fibaro home automation: device control, scenes, home/system info, variables, and quick apps. Minor gaps like advanced scheduling or bulk operations exist but don't hinder core usage.