Unkey MCP connector
The Unkey connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent create and manage API keys, identities, permissions, and deployments in Unkey as the signed-in person, with every action recorded in an audit log.
- Connects with an API key
- Free 14-day trial
- No credit card
List keys created for the Payments API this week.
Working in Unkey with Elaichi
-
Unkey analytics get verifications
-
Get single Unkey API by ID
-
Unkey apis list keys
How to connect Unkey to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Unkey 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.
Unkey 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.
Unkey 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.
Unkey 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.
Unkey 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 Unkey 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 Unkey through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Unkey is logged.
-
Engineering
Issue a key for a new customer
Ask for a new Unkey key tied to a customer's identity, with the right roles and permissions set from the start, without opening the dashboard.
-
Support
Look up a key a customer is asking about
Paste the key a customer sent in and get back which identity it belongs to, what it is allowed to do, and whether it still exists.
-
Security
Reroll a key that leaked
When a key shows up somewhere it should not, ask for it to be rerolled or deleted in Unkey right away, and confirm the old one is gone.
-
Platform
Adjust roles and permissions in bulk
Add, remove, or replace the roles and permissions on a set of Unkey keys when a plan changes or a feature moves tiers.
-
Product
See how often keys are being verified
Pull verification analytics from Unkey to find out which customers are actively calling your API and which have gone quiet.
-
Customer Success
Keep customer identities up to date
Update an identity's details in Unkey after a renewal or a name change, and list identities to check which accounts still have active keys.
Try asking
- “List keys created for the Payments API this week.”
- “Which identities have admin roles on production keys?”
- “Show verification counts by API for the last 14 days.”
What connecting Unkey gets you
6 screens from Elaichi, each doing one job for your Unkey account.
Ask Elaichi to work across your apps.
List keys created for the Payments API this week.
Which identities have admin roles on production keys?
Show verification counts by API for the last 14 days.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about keys, get real answers.
Plain questions return live Unkey keys, APIs and verification counts.
Copy the endpoint
AI apps
One Unkey endpoint, every MCP client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, no SDK, no shared key.
Tool catalog
47 Unkey tools, no custom code.
APIs, keys, identities, deployments and analytics, each with listed methods and resources.
Toolboxes
Every team gets its own toolbox.
Curate one Unkey toolbox per team, from platform to support.
Shared connections
Teammates use Unkey without touching credentials.
Each connection shows who connected it and which teams and members share it.
Audit log
Answer who rotated which Unkey key.
Append-only log records when, who, what happened, type and resource.
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.
Unkey digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch keys
Unkey
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
Unkey
Queued
Automations
A schedule fires, work finishes itself.
Fetch Unkey verifications, group them, draft a digest, approve, post back.
Unkey health
Refreshed 4 minutes ago · every 15 minutes · from the keys collection
Keys
1,284 ↓ 12%
Apis
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Keys created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
Payments API 21%
Public API 18%
Collections and dashboards
Unkey key health, computed on schedule.
Four metrics, 14 days of keys created, and a breakdown by team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Unkey
All three can connect Unkey 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 Unkey tools | Allow or restrict single Unkey 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 Unkey 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.
Unkey tools for your AI agents
47 tools are ready to call through Elaichi's MCP endpoint the moment you connect Unkey, 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 Unkey to Claude?
Connecting Unkey to Claude takes two steps. First, connect Unkey in Elaichi by pasting a root key from your Unkey dashboard, 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. Sign in with your Elaichi account and Unkey is available in Claude.
Does Unkey work with ChatGPT and Cursor as well as Claude?
Yes. Once Unkey 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 Unkey once and every client picks it up, with the same access rules and the same audit log.
What can an AI agent actually do with my Unkey data?
An agent connected to Unkey can create, look up, reroll, migrate, and delete API keys, and add, remove, or set the roles and permissions on them. It can create and update identities, create APIs and deployments, list the keys under an API, and pull verification analytics to show who is calling your API. Because Unkey has many available actions, short concrete asks such as "reroll the key for Acme" work better than long paragraphs.
Does connecting Unkey give the AI access to my whole workspace?
No. The AI acts through the Unkey root key the connecting person pasted in, so it can only reach the APIs, keys, and identities that key already covers in Unkey. Elaichi can narrow that further, for example to read-only analytics for one role, but it can never widen access beyond what the person already has.
Can I stop an agent from deleting or changing keys in Unkey?
Yes. Restrictions in Elaichi work per action, so you can allow looking up Unkey keys and reading analytics while restricting deleting keys, deleting APIs, or changing permissions. 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 a Unkey connection when someone leaves?
When a person is offboarded in Elaichi their access to Unkey through every client ends at once. If they had shared the Unkey connection with a team, it keeps working for everyone else on that team. Disconnecting Unkey in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client in one step.
Does the Unkey MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Unkey 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 Unkey?
Yes. Both let Claude, ChatGPT or Cursor use Unkey. 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 Unkey call.
How is Elaichi different from Composio for Unkey?
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 Unkey: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Unkey 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