Skip to main content
Glama
Yveshby27

brick-bacnet-mcp

by Yveshby27
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to brick-bacnet-mcp

No user-submitted related servers found.

    Related Servers

    • BACnet MCP Server

      ezhuk
      A
      license
      Not graded
      quality
      A
      maintenance
      A lightweight MCP server that connects LLM agents to BACnet devices for building automation, enabling real-time monitoring, actuation, and task orchestration.
      6
      MIT

    • MQTT MCP Server

      ezhuk
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM agents to securely monitor and control MQTT devices for building automation, industrial control, and smart home systems through a standardized MCP interface.
      25
      MIT
    • Skyforge MCP Server by skyforge-labs

      Skyforge MCP Serverofficial

      skyforge-labs
      A
      license
      Not graded
      quality
      F
      maintenance
      Connects AI assistants to SkySpark and Haxall building automation systems by dynamically exposing SkySpark Axon functions as MCP tools. Enables natural language interaction with building data, equipment, and automation functions through real-time tool discovery.
      5
      MIT

    • trane-mcp

      NoBanks
      A
      license
      A
      quality
      D
      maintenance
      Provides AI agents with read access to Trane Tracer SC+ building automation systems for inventory and telemetry retrieval.
      8
      MIT

    • x402-industrial-mcp

      xXbrucyjucyXx
      A
      license
      Not graded
      quality
      C
      maintenance
      The first and only MCP server for PLC (Programmable Logic Controller) intelligence. Give any AI agent direct access to industrial automation data — ladder logic, tag databases, cross-references, fault root cause analysis, and sequence blockers
      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

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct action: enumerating devices, listing objects per device, reading a single object's value, and retrieving the topology graph. There is no overlap in purpose, and descriptions clearly differentiate between collection-level and instance-level operations.

    Naming Consistency5/5

    All tools follow the verb_noun pattern with a clear convention: 'list_' for enumeration and 'get_' for specific retrieval. This consistency makes the tool purpose predictable and reduces cognitive load for agents.

    Tool Count5/5

    With exactly 4 tools, the server is well-scoped for a BACnet/Brick read-only exploration use case. Each tool serves an essential, non-redundant function, and the count is neither sparse nor overwhelming.

    Completeness4/5

    The tool set covers the core read workflows: discovering devices, listing their objects, reading values, and exploring the tagged topology. Minor gaps exist (e.g., no direct device detail or object write capability), but these are acceptable if the server is intended for querying rather than modification.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources