brick-bacnet-mcp
Related Servers
Alternatives to brick-bacnet-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA lightweight MCP server that connects LLM agents to BACnet devices for building automation, enabling real-time monitoring, actuation, and task orchestration.6MIT
- AlicenseNot gradedqualityAmaintenanceEnables LLM agents to securely monitor and control MQTT devices for building automation, industrial control, and smart home systems through a standardized MCP interface.25MIT

Skyforge MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceConnects 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.5MIT- AlicenseNot gradedqualityBmaintenanceA fully compliant MCP gateway and registry that federates any MCP, A2A, or REST/gRPC API behind one unified endpoint, adding centralized discovery, auth, rate limiting, retries, and OpenTelemetry observability. It virtualizes legacy services and agents into MCP-compliant tools, prompts, and resources, with 40+ plugins extending transports and protocols.Apache 2.0
- AlicenseAqualityDmaintenanceProvides AI agents with read access to Trane Tracer SC+ building automation systems for inventory and telemetry retrieval.8MIT
- AlicenseNot gradedqualityDmaintenanceThe 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 blockersMIT
TDQS
Scored across 4 tools
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.
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.
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.
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.