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 |
Capabilities
Features and capabilities supported by this server
| 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 |
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/ikari-software/fibaro-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server