brick-bacnet-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONFIG_PATH | Yes | Path to the configuration YAML file for the BACnet MCP server |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | List all BACnet devices discovered on the local broadcast domain. |
| list_objectsA | List all tagged objects for a given BACnet device. |
| get_object_valueB | Read the current present-value and tags of a single BACnet object. |
| get_tagged_topologyB | Return the full or filtered tagged-topology graph. filter_brick: keep only objects matching this Brick class fragment filter_haystack: keep only objects whose Haystack tags include all of these |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.