For the complete documentation index, see llms.txt. This page is also available as Markdown.

General Information

Note that any usage of the Elimity Insights MCP server requires a separate license. Please contact your Elimity representative for additional information.

The Elimity Insights MCP server exposes your Elimity Insights data to AI tools and agents (such as Claude and Copilot) through the Model Context Protocol (MCP), an open standard for connecting AI applications to external systems. It lets these tools query Insights on behalf of an authenticated user, rather than on a shared service account or by scraping the Insights UI.

Note: As of v1.0.0, the MCP server only supports read access. Actions that create or modify data in Elimity Insights are not yes exposed through MCP.

SaaS customers don't need to deploy or configure the MCP server themselves: Elimity hosts and manages it on their behalf, and only need to point their MCP client at the server URL communicated by their account manager. On-prem customers deploy the MCP server themselves, alongside an OAuth2 authorization server that authenticates both the incoming MCP client and the MCP server's own requests to Elimity Insights.

These pages describe how the MCP server fits together, how to deploy it on-prem, and how to configure the corresponding mcpJwtValidation settings on your Elimity Insights server.

InstallationRelease NotesStep-by-step deployment guideConnecting an MCP Client

Last updated