Security
The Auth API MCP connector
The Auth API connector brings access keys, projects, user roles, webhooks and accounts into Elaichi, so Claude, ChatGPT, Cursor or any MCP client can list, create and update them inside each person's own access.
-
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.
57 tools
How to connect
How to connect The Auth API to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect The Auth API once
-
Open Connections, choose Add connection, and pick The Auth API.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a The Auth API API key. One person generates a token in The Auth API 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 The Auth API 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 The Auth API 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 The Auth API 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 The Auth API 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 The Auth API through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Security
Audit every active access key
Ask for every access key across your The Auth API projects, spot the ones nobody recognizes, and deactivate them from the same conversation.
-
Engineering
Spin up a project with its keys
Create a new The Auth API project for a service, add the access keys it needs, and hand the details to the team without opening the console.
-
IT
Fix a locked out teammate fast
Find the deactivated access key behind a failing login and reactivate it, or update the user role that is missing, while the person is still on the call.
-
Platform
Keep webhooks pointed at the right place
List every The Auth API webhook, update the ones still calling an old URL, and send a ping to confirm each one answers before you close the ticket.
-
Support
Check a customer account before replying
Pull up a customer's The Auth API account and the role attached to it, so the answer you send is based on what is actually configured.
-
Product
Onboard a new customer account
Create the account, set its user role, and subscribe a webhook to the events the customer asked for, all in one pass.
Try asking
- “List access keys created in the last 7 days.”
- “Which projects have keys with no recent activity?”
- “Show user roles across the Payments project.”
AI tools
The Auth API tools for your AI agents
57 tools are ready to call through Elaichi's MCP endpoint the moment you connect The Auth API, 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 The Auth API gets you
6 screens from the product, each doing one job for your The Auth API account.
The agent
Ask about access keys in plain language.
The agent reads live The Auth API projects, keys and user roles to answer.
- access keys
- projects
- user roles
- members
Ask Elaichi to work across your apps.
List access keys created in the last 7 days.
Which projects have keys with no recent activity?
Show user roles across the Payments project.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint reaches Claude, ChatGPT and Cursor.
Connect The Auth API through one org MCP endpoint, no SDK, no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
57 The Auth API tools, ready to call.
Access keys, projects and user roles are covered with no custom code to write.
- List all The Auth API misc
- List all The Auth API access keys
- Create a The Auth API access key
- Update a The Auth API access key by ID
ElaichiToolsToolboxes
Every team gets its own toolbox.
Platform, Security and Support each see a curated set of The Auth API tools.
- Platform
- Security
- Engineering
- Support
ElaichiToolboxesShared connections
Share a connection, never a credential.
See who connected each The Auth API account and which teams and members use it.
- Production
- Staging
- Security
- Platform
ElaichiConnectionsAudit log
Answer who revoked that access key.
Every call records when, who, what happened, the type and the resource touched.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 fires, a person still approves.
Fetch The Auth API access keys, group them, draft a digest, approve, post back.
The Auth API digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch access keys
The Auth API
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
The Auth API
Queued
Collections and dashboards
Key health arrives before anyone asks.
Four metrics, 14 days of access keys created and a team breakdown, refreshed on schedule.
The Auth API health
Refreshed 4 minutes ago · every 15 minutes · from the access keys collection
Access keys
1,284 ↓ 12%
Projects
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Access keys created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
Security 21%
Platform 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect The Auth API to Claude?
Connect The Auth API in Elaichi first: pick it from the catalog and paste in an API key from your The Auth API console. 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 asks you to sign in to Elaichi and The Auth API is ready to use.
Does The Auth API work with ChatGPT and Cursor as well as Claude?
Yes. The Auth API is connected once in Elaichi and exposed at https://api.elaichi.ai/mcp, the same endpoint for every client. Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent all reach it through that one address, so there is nothing to set up a second time.
What can an AI agent actually do with my The Auth API data?
It can list, create, update and delete access keys, reactivate a key that was switched off, and manage projects, user roles and accounts in The Auth API. It can also list webhooks and their topics, create or update a webhook, and ping one to confirm it responds. Because The Auth API has a large set of actions, short concrete asks like "list access keys for the billing project" work better than long paragraphs.
Does connecting The Auth API give the AI access to every project and key?
No. Every call to The Auth API runs inside the access of the person who signed in to Elaichi, so the agent sees only the projects, keys, roles and accounts that person could already reach. Elaichi can narrow that further with restrictions on specific actions, and it never widens what a person can do in The Auth API.
Can I stop an agent from deleting or changing things in The Auth API?
Yes. Restrictions in Elaichi apply per action, so you can block deleting access keys, projects, user roles or webhooks in The Auth API while still allowing listing and creating. A blocked action is never shown to Claude, ChatGPT, Cursor or any other client, so no prompt, however worded, can reach it.
What happens to a The Auth API connection when someone leaves?
Offboarding a person in Elaichi ends their access to The Auth API at once, across every client they used. A shared The Auth API connection keeps working for everyone else on the team. If you want to remove The Auth API entirely, disconnecting it once in Elaichi takes it out of Claude, ChatGPT, Cursor and every other client at the same time.
Put The Auth API in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.