IM
Apono MCP connector
The Apono connector brings Apono users, groups, access flows, bundles and activity reports into Claude, ChatGPT, Cursor and any MCP client, so your team can review, create and tidy access policies in plain language.
-
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 Apono to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Apono once
-
Open Connections, choose Add connection, and pick Apono.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Apono API key. One person generates a token in Apono 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 Apono 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 Apono 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 Apono 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 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.
Use cases
What teams do with Apono through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
See it in Elaichi
What connecting Apono gets you
6 screens from the product, each doing one job for your Apono account.
The agent
Ask about access flows, get real answers.
Type a question in plain language and read live Apono users, groups and access flows.
- users
- groups
- access flows
- activity reports
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Connect any MCP client to Apono over OAuth, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
48 Apono tools ready without custom code.
Users, groups, access flows, attributes and activity reports, each with list, create and delete methods.
- List all Apono users
- Get single Apono user by ID
- List all Apono groups
- Get single Apono group by ID
Toolboxes
Every team gets its own Apono toolbox.
Curate one toolbox per team so security sees access flows and IT sees groups.
- Security
- IT operations
- Compliance
- Engineering
Shared connections
Teammates use Apono without seeing a credential.
Each connection shows who connected it and how many teams and members share it.
- Security
- IT operations
- Compliance
- Engineering
Audit log
Every Apono call is on the record.
When, who, what happened, type and resource, appended for each group and access flow change.
- 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 access review for you.
Apono activity reports are fetched, grouped, drafted into a digest, approved, then posted back.
Apono digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Apono
Queued
Collections and dashboards
Apono access numbers arrive already counted.
Four metrics, 14 days of access flows created and a team breakdown, refreshed on schedule.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 hiding actions or whole areas, 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 blocking any create, update or delete. A blocked action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.
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 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.
Put Apono in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.