Brick Bacnet MCP vs WAGO PLC
A side-by-side look at the Brick Bacnet MCP and WAGO PLC MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Brick Bacnet MCP for industrial & iot work as a local process; choose WAGO PLC for industrial & iot as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Brick Bacnet MCP when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a local stdio subprocess transport.
Choose WAGO PLC when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Industrial & IoT | Industrial & IoT |
| Quality signal | 35/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 3 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Brick Bacnet MCP | View WAGO PLC |
Tools & capabilities
Brick Bacnet MCP tools
No tool names declared yet. Check the project README from the listing page.
WAGO PLC tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Brick Bacnet MCP
{
"mcpServers": {
"brick-bacnet-mcp": {
"command": "uvx",
"args": [
"brick-bacnet-mcp"
]
}
}
}
WAGO PLC
{
"mcpServers": {
"wago-plc": {
"command": "uvx",
"args": [
"wago-plc-mcp-server"
]
}
}
}
Frequently asked questions
Brick Bacnet MCP is categorized under Industrial & IoT and uses a local stdio subprocess. WAGO PLC belongs to Industrial & IoT and uses a local stdio subprocess. Pick Brick Bacnet MCP for industrial & iot work and WAGO PLC for industrial & iot.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Brick Bacnet MCP has no declared pricing — check the project's own site. WAGO PLC has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add brick-bacnet-mcp and wago-plc as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Brick Bacnet MCP has a quality signal of 35/100 (Fair) with 2 views, 0 installs and 1 GitHub stars. WAGO PLC has 41/100 (Fair) with 0 views, 0 installs and 3 GitHub stars.