Skip to main content
Glama
ikari-software

Fibaro MCP

by ikari-software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Fibaro MCP

No user-submitted related servers found.

    Related Servers

    • Fibaro HC3 MCP Server

      kaeljune
      F
      license
      B
      quality
      D
      maintenance
      Enables control of Fibaro Home Center 3 smart home devices through natural language commands. Supports device control, scene management, lighting adjustments, and RGB color changes with automatic HC3 connection.
      13
      -

    • HC3 MCP Server

      jangabrielsson
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Fibaro Home Center 3 smart home systems through natural language commands. Provides comprehensive device control, scene management, QuickApp development, and system monitoring capabilities via the HC3 REST API.
      3
      MIT

    • hass-mcp

      hannoeru
      A
      license
      A
      quality
      F
      maintenance
      Enables controlling and querying Home Assistant devices and services via natural language. Supports state retrieval, listing states, and calling any Home Assistant service.
      13
      189 npm
      5
      MIT

    • Home Assistant MCP Server

      mjrestivo16
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Home Assistant smart home devices through natural language. Control devices, manage automations, query entity states, and retrieve historical data across your home automation system.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources