A side-by-side look at the OT AIops and Steel Brain MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose OT AIops for industrial & iot work as a local process; choose Steel Brain for industrial & iot over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose OT AIops when
You need dedicated capabilities in the Industrial & IoT domain.
No tool names declared yet. Check the project README from the listing page.
Steel Brain 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.
OT AIops is categorized under Industrial & IoT and uses a local stdio subprocess. Steel Brain belongs to Industrial & IoT and uses a remote HTTP/SSE transport. Pick OT AIops for industrial & iot work and Steel Brain 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.
OT AIops has no declared pricing — check the project's own site. Steel Brain 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 ot-aiops and steel-brain as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, OT AIops has a quality signal of 43/100 (Fair) with 2 views, 0 installs and 7 GitHub stars. Steel Brain has 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.