Factry Historian MCP
Query industrial time-series in Factry Historian from your agent and optionally link results into Grafana for ops investigations.
Overview
cloud.factry.portal/historian-mcp-server is a MCP server for the Operate phase that queries Factry Historian time-series data with JWT auth and optional Grafana explore links.
What is this MCP server?
- Stdio MCP packaged as docker.io/factry/mcp-server:0.0.5 for containerized agents
- Authenticates with FACTRY_HISTORIAN_API_TOKEN JWT against your Historian API base URL
- Requires organization UUID scoping for multi-tenant historian queries
- Optional GRAFANA_URL to emit Grafana explore links from query results
- Purpose-built for Factry Historian rather than generic SQL databases
- Registry package docker.io/factry/mcp-server:0.0.5
- Three required Historian environment variables plus optional GRAFANA_URL
- Stdio transport via OCI registryType package
What problem does it solve?
When a line or batch misbehaves, your agent cannot reach plant historian data without bespoke API scripts and manual Grafana navigation.
Who is it for?
Indie operators and small teams already on Factry Historian who want agent-driven monitoring and trace lookups.
Skip if: Builders without a Factry Historian deployment or who only need generic Postgres/Influx MCP servers.
What do I get? / Deliverables
Your agent runs historian queries scoped to your organization and can surface Grafana-friendly links for faster operational investigations.
- Agent-executed historian queries against scoped organization data
- Optional Grafana explore URLs for sharing chart context
- Repeatable ops prompts that call Historian via MCP instead of one-off scripts
Recommended MCP Servers
Journey fit
Historian access is for running production or pilot plants where traces and trends matter after something is built and deployed. Time-series queries and explore links support monitoring and incident analysis, not greenfield product ideation.
How it compares
Vertical industrial historian MCP, not a general developer-tools or code-review integration.
Common Questions / FAQ
Who is cloud.factry.portal/historian-mcp-server for?
Developers and operators using Factry Historian who want Claude Code, Cursor, or similar agents to query process data during monitoring work.
When should I use cloud.factry.portal/historian-mcp-server?
Use it in Operate when investigating production signals, validating batch behavior, or building agent-assisted runbooks against live historian tags.
How do I add cloud.factry.portal/historian-mcp-server to my agent?
Run the OCI package docker.io/factry/mcp-server:0.0.5 over stdio and set FACTRY_HISTORIAN_API_TOKEN, FACTRY_HISTORIAN_API_URL, and FACTRY_HISTORIAN_ORGANIZATION_UUID; add GRAFANA_URL if you want explore links.