Lumos MCP connector
The Lumos connector brings your apps, users, accounts, groups, roles, and activity logs into Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent, so anyone on your team can ask who has access to what and get an answer from Lumos itself.
- Connects with an API key
- Free 14-day trial
- No credit card
List Lumos apps added in the last 30 days.
Working in Lumos with Elaichi
-
List all Lumos apps
-
Get single Lumos app by ID
-
List all Lumos apps categories
How to connect Lumos to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Lumos 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.
Lumos 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.
Lumos 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.
Lumos 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.
Lumos 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 Lumos 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 Lumos through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Lumos is logged.
-
IT
Answer who has access to what
Ask which accounts a person holds across every app in Lumos, or which people hold accounts in one app, without opening a single admin console.
-
Security
Trace identity events after an alert
Pull the identity events and activity logs around a suspicious sign-in, then ask for the sequence in plain language so the picture is clear before anyone escalates.
-
Compliance
Gather evidence for an access review
List every account and role in a system that is in scope for an audit, group the results by team, and hand the reviewer a ready list instead of a spreadsheet exercise.
-
IT
Add a new app to the Lumos catalog
When the business adopts a tool, create the app in Lumos, put it in the right category, and adjust its settings from the same conversation.
-
People Ops
Confirm a leaver's accounts are closed
On someone's last day, check every account still attached to them in Lumos and flag anything that has not been removed yet.
-
Procurement
See which apps are really in use
Before a renewal, pull the app, its category, and how many accounts exist in it, so the conversation with the vendor starts from real numbers.
Try asking
- “List Lumos apps added in the last 30 days.”
- “Which Lumos users have accounts in the finance apps?”
- “Summarize app settings changed across Lumos this week.”
What connecting Lumos gets you
6 screens from Elaichi, each doing one job for your Lumos account.
Ask Elaichi to work across your apps.
List Lumos apps added in the last 30 days.
Which Lumos users have accounts in the finance apps?
Summarize app settings changed across Lumos this week.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Lumos apps, get real answers.
Question Lumos apps, users and accounts in plain language, answered from live records.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Lumos here.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
88 Lumos tools ready to call.
Apps, app settings, users, user accounts and webhooks, with no custom code.
Toolboxes
Every team gets its own Lumos toolbox.
Curate one toolbox per team so IT and Compliance see different Lumos tools.
Shared connections
Teammates use Lumos without holding credentials.
See who connected each Lumos account and how many teams and members share it.
Audit log
Every Lumos call is on the record.
When, who, what happened, type and resource, appended for each Lumos request.
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.
Lumos digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch apps
Lumos
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
Lumos
Queued
Automations
A schedule runs the whole Lumos review.
Fetch Lumos apps, group them, draft a digest, approve, then post back.
Lumos health
Refreshed 4 minutes ago · every 15 minutes · from the apps collection
Apps
1,284 ↓ 12%
App settings
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Apps created
Last 14 days
By team
Share of activity
IT Core 34%
Compliance 27%
Security Ops 21%
People Ops 18%
Collections and dashboards
Lumos health arrives before anyone asks.
Four metrics, 14 days of records created and a team breakdown, computed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Lumos
All three can connect Lumos 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 Lumos tools | Allow or restrict single Lumos 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 Lumos 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.
Lumos tools for your AI agents
88 tools are ready to call through Elaichi's MCP endpoint the moment you connect Lumos, 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 Lumos to Claude?
First connect Lumos in Elaichi, which asks for a Lumos API key and nothing else, so there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude will ask you to sign in to Elaichi, and from then on your Lumos apps, users, and accounts are available in the conversation.
Does Lumos work with ChatGPT and Cursor as well as Claude?
Yes. Once Lumos 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 Lumos once and every client sees it.
What can an AI agent actually do with my Lumos data?
With Lumos connected, an agent can look up a person and list the accounts, groups, and roles they hold, list the apps in your catalog and their categories, and read identity events and activity logs to explain what happened and when. It can also create and update apps and their settings, and upload account lists for systems Lumos does not reach on its own. Because Lumos exposes a lot of capabilities, short concrete asks such as "list Jane's accounts" work better than long paragraphs.
Does connecting Lumos give the AI access to everything in my Lumos workspace?
No. Every call into Lumos runs as the person who signed in, so the agent sees only the apps, users, and accounts that person's Lumos permissions already allow. Elaichi can narrow that further with restrictions, but it can never widen it beyond what Lumos itself grants.
Can I stop an agent from changing things in Lumos?
Yes. Restrictions in Elaichi are set per action, so you can allow reading users, accounts, and activity logs from Lumos while restricting the ability to create or update apps and settings. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.
What happens to a Lumos connection when someone leaves?
Offboarding that person in Elaichi ends their access to Lumos through every AI client at once. If they were using a shared Lumos connection, it keeps working for everyone else on the team. If you want the connection gone entirely, disconnecting Lumos once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.
Does the Lumos MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Lumos 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 Lumos?
Yes. Both let Claude, ChatGPT or Cursor use Lumos. 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 Lumos call.
How is Elaichi different from Composio for Lumos?
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 Lumos: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Lumos 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