Factry Historian MCP Server

this guide walks you through installing and running the factry historian mcp server what is this? the factry historian mcp server is a bridge that lets ai assistants (such as claude) talk to your factry historian instance it exposes historian data such as assets, measurements, event as tools an ai can call prerequisites before you start, make sure you have the following a running factry historian instance the mcp server connects to factry historian api you need the api url of your factry historian instance (e g `http //localhost 8000/api`) an api token, a token with access to factry historian docid vr6prldwhulaweklzwol your organization uuid, visible in the historian web interface under organization settings docid\ odmadpifqlvqbpgfarnxi docker docker is the software that runs containers install it from the official docker website mac / windows install https //www docker com/products/docker desktop/ linux follow the https //docs docker com/engine/install/ for your distribution to verify docker is installed, open a terminal and run docker version you should see output like docker version 27 x x installation using docker no binary installation is needed the mcp server is available as a pre built image on docker hub https //hub docker com/r/factry/mcp server/tags the recommended way to connect an ai assistant to the mcp server is via stdio transport claude desktop (or another mcp client) launches the container directly and communicates with it over stdin/stdout this means no port needs to be opened and no separate server process needs to stay running connecting claude desktop edit your claude desktop configuration file its location depends on your operating system os path macos /library/application support/claude/claude desktop config json windows %appdata%\claude\claude desktop config json linux / config/claude/claude desktop config json add the following entry under mcpservers { "mcpservers" { "factry historian" { "command" "docker", "args" \[ "run", " rm", " i", " e", "factry historian api url", " e", "factry historian api token", " e", "factry historian organization uuid", "factry/mcp server\ latest" ], "env" { "factry historian api url" "http //host docker internal 8000/api", "factry historian api token" "your token here", "factry historian organization uuid" "your organization uuid here" } } } } replace the values in env with your actual historian url, token, and organization uuid host docker internal is a special hostname that docker resolves to your host machine's ip address on linux and windows machines use it when historian is running locally on the same machine if historian is running on a different host, replace it with that host's address on linux, host docker internal requires adding add host=host docker internal\ host gateway to the args list after saving the file, fully quit and restart claude desktop open a new conversation and ask something like "what assets are available in historian?" to verify the connection optional grafana integration if you also have grafana, add the following to the env block to enable grafana related tools "grafana url" "http //host docker internal 3000", "grafana api key" "your grafana service account token" configuration reference all configuration is done through environment variables variable required default description factry historian api url yes — url to your factry historian api factry historian api token yes — token for authenticating with historian factry historian organization uuid yes — uuid of the organization in historian grafana url no — url to your grafana instance (enables grafana tools) grafana api key no — grafana service account token log level no info log verbosity debug , info , warn , error statistics disabled no false set to true to disable anonymous usage statistics troubleshooting the tools do not appear in claude desktop fully quit claude desktop (not just close the window) and restart it, configuration changes require a full restart check the claude desktop logs for errors /library/logs/claude/mcp log on macos, %appdata%\claude\logs on windows confirm docker is running and that docker run rm i factry/mcp server\ latest does not produce an error on its own the mcp server cannot reach historian if historian is running locally, make sure you are using http //host docker internal 8000/api and not http //localhost 8000/api inside a docker container, localhost refers to the container itself, not your machine on linux, add " add host=host docker internal\ host gateway" to the args list in your claude desktop config the container exits immediately run the container manually to see the error output docker run rm i \\ e factry historian api url=http //host docker internal 8000/api \\ e factry historian api token=your token \\ e factry historian organization uuid=your uuid \\ factry/mcp server\ latest