ElizaOS MCP connector
The ElizaOS connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and other MCP clients manage your ElizaOS agents, worlds, rooms and memories, start and stop agents, run jobs and generate speech, all inside each person's own ElizaOS access.
- Connects with an API key
- Free 14-day trial
- No credit card
Which ElizaOS agents are running right now?
Working in ElizaOS with Elaichi
-
List all ElizaOS agents
-
Get single ElizaOS agent by ID
-
List all ElizaOS worlds
How to connect ElizaOS to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
ElizaOS 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.
ElizaOS 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.
ElizaOS 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.
ElizaOS 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.
ElizaOS 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 ElizaOS 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 ElizaOS through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in ElizaOS is logged.
-
Product
Stand up a new agent from a brief
Describe the agent you need in plain language and have it created in ElizaOS with the right name and character, then start it when you are ready.
-
Community
Add a world for a new community
Set up a fresh ElizaOS world for a Discord server or forum, adjust its settings later, and check which agents are active there.
-
Content
Turn a script into spoken audio
Hand over a written conversation and get it back as speech, or transcribe a recorded session into text for editing and publishing.
-
Support
Correct what an agent remembers
Create a room for a customer conversation and update a stored memory so the ElizaOS agent stops repeating outdated information.
-
Operations
Pause agents outside working hours
Stop a set of ElizaOS agents at the end of the day and start them again in the morning without opening the console.
-
Engineering
Check a job and read the logs
Create a job, ask whether it is healthy, pull the system logs for a specific error and clear old entries once the problem is understood.
Try asking
- “Which ElizaOS agents are running right now?”
- “List the rooms in our main ElizaOS world.”
- “Summarize memories stored by the support ElizaOS agent.”
What connecting ElizaOS gets you
6 screens from Elaichi, each doing one job for your ElizaOS account.
Ask Elaichi to work across your apps.
Which ElizaOS agents are running right now?
List the rooms in our main ElizaOS world.
Summarize memories stored by the support ElizaOS agent.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about ElizaOS agents in plain language.
Three starter prompts pull answers from live ElizaOS agents, worlds and rooms.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.
Reach ElizaOS from any MCP client over OAuth, no SDK, no shared key.
Tool catalog
82 ElizaOS tools arrive ready to call.
Agents, worlds, rooms, memories and audio methods, with no custom code written.
Toolboxes
Every team gets its own ElizaOS toolbox.
Curate one toolbox per team so each group sees the ElizaOS tools it needs.
Shared connections
Teammates use ElizaOS without seeing credentials.
The connections table shows who connected each account and which teams share it.
Audit log
Every ElizaOS call is answerable later.
When, who, what happened, type and resource, appended for each agent and world.
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.
ElizaOS digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch agents
ElizaOS
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
ElizaOS
Queued
Automations
A schedule drafts your ElizaOS agent digest.
Six steps fetch and group agents, draft a digest, await approval, then post back.
ElizaOS health
Refreshed 4 minutes ago · every 15 minutes · from the agents collection
Agents
1,284 ↓ 12%
Worlds
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Agents created
Last 14 days
By team
Share of activity
AI Platform 34%
Support Voice 27%
Research Lab 21%
Product EMEA 18%
Collections and dashboards
ElizaOS agent health, counted not narrated.
Four metrics, 14 days of records created, and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for ElizaOS
All three can connect ElizaOS 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 ElizaOS tools | Allow or restrict single ElizaOS 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 ElizaOS 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.
ElizaOS tools for your AI agents
82 tools are ready to call through Elaichi's MCP endpoint the moment you connect ElizaOS, 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 ElizaOS to Claude?
First connect ElizaOS in Elaichi by pasting in your ElizaOS API key, 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 the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Claude can start working with your ElizaOS agents, worlds and memories.
Does ElizaOS work with ChatGPT and Cursor as well as Claude?
Yes. Once ElizaOS 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 ElizaOS once and every client you use picks it up.
What can an AI agent actually do with my ElizaOS data?
It can list your ElizaOS agents, create or update one, start and stop them, and set up or adjust the worlds and rooms they live in. It can update a stored memory, create and check jobs, read or clear system logs, upload media for an agent or a channel, and generate speech or transcribe audio. Because ElizaOS exposes many actions, short concrete asks such as "stop the support agent" work better than long paragraphs.
Does connecting ElizaOS give the AI access to every agent and world?
No. Every request runs inside the ElizaOS access of the person who signed in, so the AI sees exactly the agents, worlds and logs that person can already reach in ElizaOS. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what the person holds.
Can I stop an agent from deleting or changing things in ElizaOS?
Yes. Restrictions in Elaichi apply per action, so you can allow listing and starting ElizaOS agents while restricting deleting an agent, clearing logs or updating memories. 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 ElizaOS connection when someone leaves?
When you offboard a person in Elaichi their access to ElizaOS through every client ends at once. A shared ElizaOS connection keeps working for everyone else on the team. If you want to remove ElizaOS entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the ElizaOS MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. ElizaOS 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 ElizaOS?
Yes. Both let Claude, ChatGPT or Cursor use ElizaOS. 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 ElizaOS call.
How is Elaichi different from Composio for ElizaOS?
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 ElizaOS: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put ElizaOS 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