Factry Historian MCP
LocalAbout Factry Historian MCP
MCP server for querying Factry Historian
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
docker run -i --rm -e FACTRY_HISTORIAN_API_TOKEN -e FACTRY_HISTORIAN_API_URL -e FACTRY_HISTORIAN_ORGANIZATION_UUID -e GRAFANA_URL -e GRAFANA_API_KEY docker.io/factry/mcp-server:0.0.6FACTRY_HISTORIAN_API_TOKENSecretJWT token used to authenticate against Factry Historian APIFACTRY_HISTORIAN_API_URLBase URL to the Factry Historian APIFACTRY_HISTORIAN_ORGANIZATION_UUIDOrganization UUID used for historian queriesGRAFANA_URLOptional Grafana base URL for generated explore linksGRAFANA_API_KEYSecretOptional Grafana API keyLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.