> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/mcp-general-information/general-information.md).

# General Information

{% hint style="info" %}
Note that any usage of the Elimity Insights MCP server requires a separate license. Please contact your Elimity representative for additional information.
{% endhint %}

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](https://modelcontextprotocol.io) (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.

{% content-ref url="/spaces/UYOtmS0JmAI0xHx8RpgQ/pages/X3aTRttZSw1HanWjMmuc" %}
[Installation](/mcp-reference-manual/installation.md)
{% endcontent-ref %}

{% content-ref url="/pages/VmypK0vg1rvqFOK5ydq0" %}
[Release Notes](/mcp-general-information/release-notes/v1.2.1.md)
{% endcontent-ref %}

{% content-ref url="/spaces/UYOtmS0JmAI0xHx8RpgQ/pages/JyQIwXNby2xBBLD41guW" %}
[Step-by-step deployment guide](/mcp-reference-manual/step-by-step-deployment-guide.md)
{% endcontent-ref %}

{% content-ref url="/spaces/UYOtmS0JmAI0xHx8RpgQ/pages/YCiurH7TeuJ1HwxbIKEY" %}
[Connecting an MCP Client](/mcp-reference-manual/connecting-an-mcp-client.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.elimity.com/mcp-general-information/general-information.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.