IM
Apono MCP connector
The Apono connector brings Apono users, groups, access flows, bundles and activity reports into Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so your team can review, create and tidy access policies in plain language.
- Connects with an API key
- Free 14-day trial
- No credit card
Claude
Elaichi connected
Which Apono access flows grant production access this month?
Working in Apono with Elaichi
-
List all Apono users
-
-
Governance
/
Audit log
Last 24 hours
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
ChatGPT · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Apono to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Apono 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.
Apono 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.
Apono 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.
Apono 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.
Apono 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 Apono 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 Apono through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Apono is logged.
-
Security
Review who can request what
Ask which access flows exist, who they apply to and what they grant, then spot the one that has drifted from policy before it becomes a finding.
-
IT
Set up access for a new team
Describe the new team's needs and have the agent create the Apono group, bundle the resources they need and draft the access flow that ties them together.
-
Compliance
Pull an activity report before an audit
Create an Apono activity report for the quarter, fetch the results and get a plain summary of who was granted access to what, ready for the auditor.
-
Platform
Adjust an on-call bundle in minutes
Update the bundle your on-call engineers request when a new database or cluster comes online, without opening the Apono console.
-
IT
Clean up groups after a reorg
List every Apono group, find the ones nobody belongs to anymore and remove them, with each deletion recorded in the audit log.
-
Security
Check which systems Apono covers
Ask which cloud accounts and tools Apono is connected to and which user attributes are available, so you know where an access flow can actually reach.
Try asking
- “Which Apono access flows grant production access this month?”
- “List Apono groups with no members.”
- “Summarize last week's Apono activity reports by requester.”
What connecting Apono gets you
6 screens from Elaichi, each doing one job for your Apono account.
Ask Elaichi to work across your apps.
Which Apono access flows grant production access this month?
List Apono groups with no members.
Summarize last week's Apono activity reports by requester.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about access flows, get real answers.
Type a question in plain language and read live Apono users, groups and access flows.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.
Connect any MCP client to Apono over OAuth, with no SDK and no shared API key.
ElaichiToolsTool catalog
48 Apono tools ready without custom code.
Users, groups, access flows, attributes and activity reports, each with list, create and delete methods.
ElaichiToolboxesToolboxes
Every team gets its own Apono toolbox.
Curate one toolbox per team so security sees access flows and IT sees groups.
ElaichiConnectionsShared connections
Teammates use Apono without seeing a credential.
Each connection shows who connected it and how many teams and members share it.
ElaichiAudit logAudit log
Every Apono call is on the record.
When, who, what happened, type and resource, appended for each group and access flow change.
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.
Apono digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Apono
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
Apono
Queued
Automations
A schedule runs the access review for you.
Apono activity reports are fetched, grouped, drafted into a digest, approved, then posted back.
Apono health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Groups
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Security 34%
IT operations 27%
Compliance 21%
Engineering 18%
Collections and dashboards
Apono access numbers arrive already counted.
Four metrics, 14 days of access flows created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Apono
All three can connect Apono 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 Apono tools | Allow or restrict single Apono 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 Apono 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.
Apono tools for your AI agents
48 tools are ready to call through Elaichi's MCP endpoint the moment you connect Apono, 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 Apono to Claude?
Connect Apono in Elaichi by pasting an Apono API key, then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Apono connects with an API key, so there is no OAuth application to register and no client ID or secret to generate. Once the endpoint is in Claude, sign in to Elaichi and Apono is ready to use.
Does Apono work with ChatGPT and Cursor as well as Claude?
Yes. Once Apono 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 Apono once and every client you use picks it up.
What can an AI agent actually do with my Apono data?
With Apono connected, an agent can look up users and groups, list and explain access flows, create or update bundles of resources, and create, fetch or update activity reports. It can also tell you which systems Apono is connected to and which user attributes are available for policies. Because Apono exposes many actions, short concrete asks such as "list access flows for the finance group" work better than long paragraphs.
Does connecting Apono give the AI access to every access flow and user?
No. Every call to Apono runs inside the access of the person who signed in to Elaichi, so the agent sees only what that person's Apono API key can see. Elaichi can narrow that further by restricting single actions or the whole connector, but it can never widen what Apono itself allows.
Can I stop an agent from deleting or changing things in Apono?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Apono access flows and reports while restricting any create, update or delete. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to an Apono connection when someone leaves?
Offboarding a person in Elaichi ends their access to Apono through every client at once, including Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent. If the Apono connection was shared, it keeps working for everyone else on the team. Disconnecting Apono once in Elaichi removes it from every client for everyone.
Does the Apono MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Apono 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 Apono?
Yes. Both let Claude, ChatGPT or Cursor use Apono. 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 Apono call.
How is Elaichi different from Composio for Apono?
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 Apono: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Apono 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