Lenses MCP connector
The Lenses connector lets Claude, ChatGPT, Cursor, Microsoft Copilot 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.
- Connects with an API key
- Free 14-day trial
- No credit card
List Lenses environments and the Kafka connections each one uses.
Working in Lenses with Elaichi
-
List all Lenses environments
-
Get single Lenses environment by ID
-
List all Lenses environment kafka connections
How to connect Lenses to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Lenses MCP connector for 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.
Lenses MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Lenses MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
Lenses MCP connector for 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.
Lenses MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Lenses through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Lenses is logged.
-
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.”
What connecting Lenses gets you
6 screens from Elaichi, each doing one job for your Lenses account.
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, Cursor or Microsoft Copilot
The agent
Ask about Lenses environments in plain language.
Starter prompts return answers from live Lenses environments, groups and Kafka connections.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Lenses here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
258 Lenses tools arrive ready to call.
Environments, Kafka connections, groups and keys are covered with no custom code.
Toolboxes
Each team gets its own Lenses toolbox.
Platform, data and security teams see only the Lenses toolbox scoped to them.
Shared connections
Teammates use Lenses without seeing a credential.
Each connection shows who connected it and how many teams and members share it.
Audit log
Every Lenses call is written down.
When, who, what happened, type and resource for each environment or group touched.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Lenses digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Lenses
Queued
Automations
A schedule runs the Lenses digest for you.
Six steps fetch environments, group them, draft a digest, await approval, post back.
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%
Collections and dashboards
Lenses health arrives counted, not requested.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Lenses
All three can connect Lenses to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Lenses tools | Allow or restrict single Lenses tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Lenses call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting deletes, updates or key renewals. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot and every other client in one step.
Does the Lenses MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Lenses is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Lenses?
Yes. Both let Claude, ChatGPT or Cursor use Lenses. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Lenses call.
How is Elaichi different from Composio for Lenses?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Lenses: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Lenses in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot