# MCP Server The historian MCP is hosted as part of the Historian Data API on the following endpoint: ``` /api/historian/v3/mcp ``` Please note that the server does not support connection via the deprecated STDIO standard. ## Authentication Authentication works in the same way as all calls in the Historian Data API. You must include *x-api-key* as a header: ``` x-api-key: YOUR_KEY ``` Keys can be managed via the MobiusFlow View application. ## Tools All tools are exposed when connecting to the MCP server. Currently available tools include: * get-all-objects-name-uri-map * get-closest-matching-object-by-name * get-telemetry-for-mulitple-series * get-profiles Input formats for all tools can be obtained by connecting to the MCP server. Documentation for output formats is coming soon, however is not normally required for agentic application. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.mobiusflow.com/help/mobiusflow-v3/mobiusflow-historian-data-api-v3/mcp-server.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.