Brick Bacnet MCP vs Opcua MCP
A side-by-side look at the Brick Bacnet MCP and Opcua MCP 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 Opcua MCP for industrial & iot. 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 Opcua MCP when
- You need dedicated capabilities in the Industrial & IoT domain.
- Its auth model fits you: No auth required.
- You have the keys it needs:
OPCUA_SERVER_URL. - You want tools like
Description, Returns.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Industrial & IoT | Industrial & IoT |
| Quality signal | 35/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | OPCUA_SERVER_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 30 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Brick Bacnet MCP | View Opcua MCP |
Tools & capabilities
Brick Bacnet MCP tools
No tool names declared yet. Check the project README from the listing page.
Opcua MCP tools 2
DescriptionRead the value of a specific OPC UA node.ReturnsA string with the node ID and its value (e.g., "Node ns=2;i=2 value: 42").
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"
]
}
}
}
Opcua MCP
No confirmed install command for Opcua MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Brick Bacnet MCP is categorized under Industrial & IoT and uses a local stdio subprocess. Opcua MCP belongs to Industrial & IoT and uses an install path we have not confirmed yet. Pick Brick Bacnet MCP for industrial & iot work and Opcua MCP 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. Opcua MCP has no confirmed install command yet — follow its own setup instructions.
Brick Bacnet MCP has no declared pricing — check the project's own site. Opcua MCP is listed as free. Auth: no auth required. 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 kukapay-opcua-mcp 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. Opcua MCP has 37/100 (Fair) with 4 views, 0 installs and 30 GitHub stars.