OpenAI MCP connector
The OpenAI connector lets Claude, ChatGPT, Cursor, or any MCP client manage your OpenAI organization's users, projects, service accounts, API keys, and rate limits, with each person acting within their own access and every change logged.
-
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 OpenAI to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect OpenAI once
-
Open Connections, choose Add connection, and pick OpenAI.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an OpenAI API key. One person generates a token in OpenAI 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.
OpenAI 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.
OpenAI 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 today. The plugin directory lives at chatgpt.com/plugins.
OpenAI 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.
Connect OpenAI 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 OpenAI through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
IT
Add a new hire to the right OpenAI projects
Ask for a new teammate to be added to the OpenAI organization and given membership in the projects their team uses, with the role you name. What used to be three admin screens becomes one request.
-
Security
Find and revoke stale project API keys
List every API key across your OpenAI projects, spot the ones nobody recognizes or that belong to a service account that should have been retired, and revoke them on the spot.
-
Finance
Keep OpenAI spend inside project rate limits
Review the rate limits set on each OpenAI project and tighten the ones for pilots or experiments so a runaway script cannot run up an unexpected bill.
-
Engineering
Set up a project for a new application
Create an OpenAI project for a new product, add a service account for it, and add the engineers who will work on it, all from the chat window you are already in.
-
People
Offboard a leaver from OpenAI in one ask
When someone leaves, remove them from every OpenAI project they were in and from the organization itself, then confirm nothing they created is still active.
-
Operations
Answer who has access to which OpenAI project
Pull a plain list of OpenAI projects with their members, service accounts, and keys, and archive projects that have gone quiet, so the organization stays tidy and reviewable.
Try asking
- “Which OpenAI projects have no project users left?”
- “List OpenAI users added to Platform Core this month.”
- “Summarize archived OpenAI projects and who owned them.”
Compare
Elaichi vs Zapier MCP vs Composio for OpenAI
All three can connect OpenAI 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 OpenAI tools | Allow or restrict single OpenAI 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 OpenAI 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 | $15 per user per month. | 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.
AI tools
OpenAI tools for your AI agents
157 tools are ready to call through Elaichi's MCP endpoint the moment you connect OpenAI, 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 OpenAI gets you
6 screens from the product, each doing one job for your OpenAI account.
The agent
Ask about OpenAI projects, get answers.
Plain language questions read live OpenAI users, projects and project members.
- users
- projects
- project users
- invites
Ask Elaichi to work across your apps.
Which OpenAI projects have no project users left?
List OpenAI users added to Platform Core this month.
Summarize archived OpenAI projects and who owned them.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One OpenAI endpoint for every MCP client.
Claude, ChatGPT and Cursor connect over OAuth, no SDK, no shared API key.
Copy the endpoint
Tool catalog
157 OpenAI tools ready without custom code.
Browse OpenAI users, projects and project user methods in one catalog.
- List all OpenAI users
- Get single OpenAI user by ID
- Delete a OpenAI user by ID
- Update a OpenAI user by ID
Toolboxes
Every team gets its own OpenAI toolbox.
Curate OpenAI tools per team so each group sees only its scope.
- Platform Engineering
- Data Science
- IT Operations
- Security
Shared connections
Share OpenAI accounts, never the credential.
See who connected each OpenAI account and how many teams and members use it.
- Platform Core
- Research Sandbox
- IT Admin
- Data Science
Audit log
Every OpenAI call is on the record.
When, who, what happened, type and resource for each OpenAI project 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 drafts your OpenAI project digest.
Six steps fetch OpenAI projects, group them, draft, wait for approval, then post back.
OpenAI digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
OpenAI
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
OpenAI
Queued
Collections and dashboards
OpenAI project health, counted on a schedule.
Four metrics, 14 days of projects created and a per team breakdown, no model.
OpenAI health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Projects
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Platform Core 34%
Research Sandbox 27%
IT Admin 21%
Data Science 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect OpenAI to Claude?
Two steps. In Elaichi, choose OpenAI and paste an OpenAI admin API key when asked; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in with your Elaichi account and OpenAI is available in Claude.
Does OpenAI work with ChatGPT and Cursor as well as Claude?
Yes. Once OpenAI 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 OpenAI once and every client you use picks it up.
What can an AI agent actually do with my OpenAI organization?
With OpenAI connected, an agent can list and update the people in your OpenAI organization, create, update, and archive projects, add or remove project members, create and delete service accounts, review and revoke project API keys, and adjust project rate limits. Because OpenAI exposes a large set of actions, short concrete asks such as "list API keys in the Marketing project" work better than long paragraphs.
Does connecting OpenAI give the AI full control of the organization?
No. Every action in OpenAI runs inside the access of the person who signed in to Elaichi, so an agent can only see and change what that person's OpenAI role allows. Elaichi can narrow that further with restrictions, but it can never widen it beyond what OpenAI already grants.
Can I stop an agent from deleting users or revoking API keys in OpenAI?
Yes. Restrictions in Elaichi apply per action, so you can allow listing OpenAI projects and members while blocking the actions that delete users, revoke API keys, or archive projects. A blocked action is never shown to Claude, ChatGPT, or any other client, so no prompt, however worded, can reach it.
What happens to an OpenAI connection when someone leaves?
Offboarding a person in Elaichi ends their access to OpenAI through every client at once. A shared OpenAI connection keeps working for everyone else on the team, because it does not depend on the leaver's login. If you ever want OpenAI gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.
Does the OpenAI MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. OpenAI 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, 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 OpenAI?
Yes. Both let Claude, ChatGPT or Cursor use OpenAI. 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 OpenAI call.
How is Elaichi different from Composio for OpenAI?
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 OpenAI: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put OpenAI in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.