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

# Overview

This page provides an overview of the Lenses MCP server.

This is the MCP (Model Context Protocol) server for [Lenses](https://lenses.io/kafka-ai), a self-service DataOps tool. With Lenses, you can find, explore, transform, integrate, and replicate data across a multi-Kafka and vendor estate. All this power is accessible to your AI tools (such as Cursor, Claude Code, and Codex) and your AI Agents via the Lenses MCP Server.

Lenses MCP Server is built for enterprise use cases with OAuth to grant read, write and delete authorization scopes. It follows [RFC 7591](https://datatracker.ietf.org/doc/html/rfc7591): Dynamic Client Registration (DCR) and falls back to authentication with an API key (provisioned via a service account in Lenses DevX).

Try it by downloading [Lenses Community Edition](https://lenses.io/community-edition/) (free, but with restricted number of users and enterprise features, e.g. SSO).


---

# 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 dynamically by asking a question.

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

```
GET https://docs.lenses.io/latest/mcp/overview.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 `build a script that syncs our docs to a CMS` 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.