Analytics
Lenses MCP connector
The Lenses connector lets Claude, ChatGPT, Cursor and other AI clients list and manage Lenses environments, Kafka connections, users and groups, with every action running as the signed-in person and recorded in an audit log.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Lenses to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Lenses once
-
Open Connections, choose Add connection, and pick Lenses.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Lenses API key. One person generates a token in Lenses and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Lenses to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Lenses to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Lenses to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Lenses to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Lenses through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Data platform
See every Lenses environment at a glance
Ask for a rundown of all Lenses environments and the Kafka connection behind each one before a release or an on-call handover. Follow up on a single environment by name to get its full details.
-
Platform engineering
Stand up a new environment for a project
Create a Lenses environment for a new team or region, then adjust its details as the project settles. Retire it cleanly when the work is done.
-
Platform engineering
Fix a Kafka connection after a cluster move
When brokers change, update the Kafka connection on the affected Lenses environment so it points at the right cluster. Confirm the change by asking for the connection details back.
-
Security
Rotate an environment key on schedule
Renew the key for a Lenses environment as part of a rotation policy or after someone with access moves on. Ask for the list of environments first so none are missed.
-
IT
Onboard a new engineer into Lenses
Create the Lenses user, drop them into the right groups and check their settings in one conversation. Update several profiles or group memberships at once when a whole cohort joins.
-
Compliance
Review who has access to Lenses
Pull the full list of Lenses users and groups, spot accounts that should no longer exist and remove them. Have the AI summarize group membership for an access review.
Try asking
- “List Lenses environments and the Kafka connections each one uses.”
- “Which Lenses groups changed this week, and who updated them?”
- “Summarize Kafka connections per Lenses environment for Thursday's platform review.”
AI tools
Lenses tools for your AI agents
258 tools are ready to call through Elaichi's MCP endpoint the moment you connect Lenses, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Lenses gets you
6 screens from the product, each doing one job for your Lenses account.
The agent
Ask about Lenses environments in plain language.
Starter prompts return answers from live Lenses environments, groups and Kafka connections.
- environments
- kafka connections
- groups
- keys
Ask Elaichi to work across your apps.
List Lenses environments and the Kafka connections each one uses.
Which Lenses groups changed this week, and who updated them?
Summarize Kafka connections per Lenses environment for Thursday's platform review.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Lenses here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
258 Lenses tools arrive ready to call.
Environments, Kafka connections, groups and keys are covered with no custom code.
- List all Lenses environments
- Create a Lenses environment
- Get single Lenses environment by ID
- Update a Lenses environment by ID
Toolboxes
Each team gets its own Lenses toolbox.
Platform, data and security teams see only the Lenses toolbox scoped to them.
- Platform engineering
- Data engineering
- Security
- SRE
Shared connections
Teammates use Lenses without seeing a credential.
Each connection shows who connected it and how many teams and members share it.
- Platform prod
- Platform staging
- Data engineering
- Security
Audit log
Every Lenses call is written down.
When, who, what happened, type and resource for each environment or group touched.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule runs the Lenses digest for you.
Six steps fetch environments, group them, draft a digest, await approval, post back.
Lenses digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch environments
Lenses
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Lenses
Queued
Collections and dashboards
Lenses health arrives counted, not requested.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
Lenses health
Refreshed 4 minutes ago · every 15 minutes · from the environments collection
Environments
1,284 ↓ 12%
Kafka connections
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Environments created
Last 14 days
By team
Share of activity
Platform prod 34%
Platform staging 27%
Data engineering 21%
Security 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Lenses to Claude?
Connecting Lenses takes two steps. In Elaichi, add the Lenses connector and paste in a Lenses API key, then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register for Lenses and no client ID or secret to generate. Once Claude is connected you sign in to Elaichi as yourself and start asking about your Lenses environments.
Does Lenses work with ChatGPT and Cursor as well as Claude?
Yes. Once Lenses is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Lenses once and every client you use sees it.
What can an AI agent actually do with my Lenses data?
An agent connected to Lenses can list your Lenses environments and the Kafka connection behind each one, create or update an environment, fix a Kafka connection after a cluster change and renew an environment key. It can also add, update or remove Lenses users and groups, update several user profiles or group memberships at once and review user settings. Because Lenses exposes a large set of actions, short concrete asks such as "list Lenses environments" work better than long paragraphs.
Does connecting Lenses give the AI access to every environment and user?
No. Every request to Lenses runs inside the access of the person who signed in to Elaichi, so the AI can only see the Lenses environments, Kafka connections, users and groups that person could already manage. Elaichi can narrow that further, for example to read-only, but it can never widen what Lenses itself allows.
Can I stop an agent from deleting or changing things in Lenses?
Yes. Restrictions in Elaichi apply per action, so you can allow listing and viewing Lenses environments and users while blocking deletes, updates or key renewals. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it.
What happens to a Lenses connection when someone leaves?
When a person is offboarded in Elaichi, their access to Lenses through every AI client ends at once. A shared Lenses connection keeps working for everyone else on the team. If you disconnect Lenses in Elaichi, it disappears from Claude, ChatGPT, Cursor and every other client in one step.
Put Lenses in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.