MergenHub MCP Server — query the plant in natural language
The Model Context Protocol server that connects AI assistants to your plant. It answers status, alarm, trend and diagnostic questions in natural language — secure and read-only.
What it does
The MCP Server exposes MergenHub data to AI assistants over the Model Context Protocol. The assistant answers questions like "which pumps are in alarm?" or "tank level trend over the last hour" through tool calls. The JSON-RPC /mcp endpoint is protected with a bearer token.
Key features
Two-layer authorization: token scope ∩ live Capability — the assistant sees only permitted data. OAuth 2.0 PKCE + DCR is supported end-to-end. Critical safety principle: the MCP surface is read-only; there are no writes or mutations.
Core capabilities
JSON-RPC /mcp
Standard Model Context Protocol endpoint; tool-based queries.
Bearer + OAuth 2.0
End-to-end authentication with a bearer token (mhmcp_) and OAuth 2.0 PKCE + DCR.
Two-layer
Intersection of token scope and live Capability — the assistant sees only authorized resources.
Status & alarms & trends
Node status, alarm events, tag history, metrics and diagnostic queries.
Read-only
The MCP surface performs no writes/mutations — the assistant cannot change the plant.
Rich tool set
Tools for node listing, live values, tag history, alarm lists and system status.