> 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/lenses-mcp-server/getting-started/run-with-community-edition.md).

# Run with Community Edition

The fastest way to try the MCP server is to use Lenses Community Edition, which runs Lenses MCP Server as a remote server and comes with a pre-configured single broker Kafka cluster with demo data.

{% stepper %}
{% step %}

### Download and run Lenses Community Edition

To set up and run, follow the [Lenses Community Edition setup instructions](https://docs.lenses.io/latest/getting-started/quickstart).

Lenses MCP Server runs on <http://localhost:8000/> with `OAUTH_ENABLED` set to `True`. OAuth is enabled by default.
{% endstep %}

{% step %}

### Configure in your AI tool

To run in Cursor, Claude, Codex, or another client, use this `mcp.json` configuration. It connects the client using HTTP transport:

```json
{
  "mcpServers": {
    "Lenses": {
      "type": "http",
      "url": "http://localhost:8000/mcp"
    }
}
```

{% endstep %}

{% step %}

### Authenticate using OAuth

Navigate to your AI tool's MCP server settings and connect to authenticate with the Lenses OAuth authorization server (visible to your AI tool's client, configured with `LENSES_ADVERTISED_URL` with value <http://localhost:9991/>). Here is an example using Cursor.

<figure><img src="https://3513156164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOPahZVG0l6oMQ9aqD8Vq%2Fuploads%2F6ZSMkkooB2UtwXAP5t2v%2Fimage.png?alt=media&amp;token=f105dc45-1e0f-48d1-a744-66ecc14d415b" alt="Cursor MCP server settings"><figcaption></figcaption></figure>

This opens a web browser at <http://localhost:9991/oauth2/authorize> and passes OAuth parameters. Log in with your username/password. The default credentials are `admin`:`admin`.

<figure><img src="https://3513156164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOPahZVG0l6oMQ9aqD8Vq%2Fuploads%2FL0yKwmCNZbN7NZ6pb0ZG%2Fimage.png?alt=media&amp;token=05a495e4-ac2d-467e-8fdc-5341b881c4b3" alt="Lenses login screen"><figcaption></figcaption></figure>

The authorization server displays an OAuth consent screen. Set the read, write, and delete scopes.

<figure><img src="https://3513156164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOPahZVG0l6oMQ9aqD8Vq%2Fuploads%2FsAMZ543R6OZwfNJlESmZ%2Fimage.png?alt=media&amp;token=f9eaf6b1-803a-45a5-9c69-59600b19d100" alt="OAuth authorization consent screen"><figcaption></figcaption></figure>

After you complete this flow, your AI tool authenticates with Lenses MCP Server using the granted scopes.

<figure><img src="https://3513156164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOPahZVG0l6oMQ9aqD8Vq%2Fuploads%2FJDnYTokeSeOLcNnA86oD%2Fimage.png?alt=media&amp;token=68035247-5684-4721-a753-f8943fc54a5a" alt="Authenticated Lenses MCP Server connection in Cursor"><figcaption></figcaption></figure>

{% hint style="info" %}
Lenses documentation is available on [Context7](https://context7.com/websites/lenses_io). Use the [Context7 MCP Server](https://github.com/upstash/context7) and adjust your prompts with `use context7` to ensure your AI tool has the latest documentation.
{% endhint %}
{% endstep %}
{% endstepper %}


---

# 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/lenses-mcp-server/getting-started/run-with-community-edition.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.