Artificial Intelligence
ElizaOS MCP connector
The ElizaOS connector lets Claude, ChatGPT, Cursor 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.
-
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.
82 tools
How to connect
How to connect ElizaOS to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect ElizaOS once
-
Open Connections, choose Add connection, and pick ElizaOS.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an ElizaOS API key. One person generates a token in ElizaOS 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 ElizaOS 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 ElizaOS 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 ElizaOS 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 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.
Use cases
What teams do with ElizaOS through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
See it in Elaichi
What connecting ElizaOS gets you
6 screens from the product, each doing one job for your ElizaOS account.
The agent
Ask about ElizaOS agents in plain language.
Three starter prompts pull answers from live ElizaOS agents, worlds and rooms.
- agents
- worlds
- rooms
- memories
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Reach ElizaOS from any MCP client over OAuth, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
82 ElizaOS tools arrive ready to call.
Agents, worlds, rooms, memories and audio methods, with no custom code written.
- List all ElizaOS agents
- Create a ElizaOS agent
- Get single ElizaOS agent by ID
- Update a ElizaOS agent by ID
ElaichiToolsToolboxes
Every team gets its own ElizaOS toolbox.
Curate one toolbox per team so each group sees the ElizaOS tools it needs.
- AI Platform
- Support
- Voice
- Research
ElaichiToolboxesShared connections
Teammates use ElizaOS without seeing credentials.
The connections table shows who connected each account and which teams share it.
- AI Platform
- Support Voice
- Research Lab
- Product EMEA
ElaichiConnectionsAudit log
Every ElizaOS call is answerable later.
When, who, what happened, type and resource, appended for each agent and world.
- 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 drafts your ElizaOS agent digest.
Six steps fetch and group agents, draft a digest, await approval, then post back.
ElizaOS digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
ElizaOS
Queued
Collections and dashboards
ElizaOS agent health, counted not narrated.
Four metrics, 14 days of records created, and a team breakdown, refreshed on schedule.
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%
FAQ
Frequently asked questions
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, 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 blocking deleting an agent, clearing logs or updating memories. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt can reach it.
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 and every other client.
Put ElizaOS in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.