# 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.

Source: https://elaichi.ai/connectors/elizaos/

## Facts

| | |
| --- | --- |
| Application | ElizaOS |
| Category | Artificial Intelligence |
| AI tools | 82 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once ElizaOS is connected

- Which ElizaOS agents are running right now?
- List the rooms in our main ElizaOS world.
- Summarize memories stored by the support ElizaOS agent.

## Connect ElizaOS in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick ElizaOS.
2. Optionally set Share with, then press Connect.
3. 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.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which ElizaOS tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## ElizaOS MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## ElizaOS MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete data and remove access", which you tick yourself. Calling a ElizaOS tool needs "Run your connected tools". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Run your connected tools, which can also delete in connected apps and cannot be undone.

## What teams do with ElizaOS through Elaichi

### Stand up a new agent from a brief

Product. 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.

### Add a world for a new community

Community. Set up a fresh ElizaOS world for a Discord server or forum, adjust its settings later, and check which agents are active there.

### Turn a script into spoken audio

Content. Hand over a written conversation and get it back as speech, or transcribe a recorded session into text for editing and publishing.

### Correct what an agent remembers

Support. Create a room for a customer conversation and update a stored memory so the ElizaOS agent stops repeating outdated information.

### Pause agents outside working hours

Operations. Stop a set of ElizaOS agents at the end of the day and start them again in the morning without opening the console.

### Check a job and read the logs

Engineering. 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.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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, 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 my team share one ElizaOS connection?

Yes. One person connects ElizaOS in Elaichi and shares the connection with a team, so nobody else ever has to handle the ElizaOS API key. Each teammate still signs in to Elaichi as themselves, so every action against an ElizaOS agent or world is recorded under their own name in the audit log.

### 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.

## All 82 ElizaOS tools

Every tool below is callable through https://api.elaichi.ai/mcp once ElizaOS is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all ElizaOS agents** (List). List all ElizaOS agents. Returns each agent's id and name. No required parameters.
- **Create a ElizaOS agent** (Create). Create a new agent in ElizaOS from a character path or inline JSON. Returns: id, name, bio, settings, system, style, lore, messageExamples, topics, plugins. Provide either characterPath or characterJson.
- **Get single ElizaOS agent by ID** (Get). Get details of a single ElizaOS agent by id. Returns the agent's id and name. Required: id.
- **Update a ElizaOS agent by ID** (Update). Update an existing ElizaOS agent by id. Returns: id, name. Required: id.
- **Delete a ElizaOS agent by ID** (Delete). Delete an ElizaOS agent by id. Returns: success, message. Required: id.
- **ElizaOS agents start** (Start). Start an elizaos agent. Returns the started agent object under data including id, name, and status. Required: agent_id.
- **ElizaOS agents stop** (Stop). Stop an elizaos agent. Returns a success flag and a data.message confirmation. Required: agent_id.
- **List all ElizaOS worlds** (List). List all worlds in elizaos. Returns: id, name, agentId, sourceType, sourceId, metadata.
- **Create a ElizaOS world** (Create). Create a world for an elizaos agent. Returns the world object. Required: agent_id, name, sourceType, sourceId.
- **Update a ElizaOS world by ID** (Update). Update an elizaos world. Returns the world object. Required: agent_id, id.
- **ElizaOS audio generate speech** (Generate). Generate speech from text for an elizaos agent. Returns the generated audio as an audio/mpeg file. Required: agent_id, text.
- **ElizaOS audio synthesize speech** (Action). Synthesize speech from text for an elizaos agent. Returns the generated audio/mpeg file. Required: agent_id, text.
- **ElizaOS audio convert conversation to speech** (Convert). Convert a conversation to speech for an elizaos agent. Returns the generated audio/mpeg file. Required: agent_id, messages.
- **ElizaOS audio transcribe** (Action). Transcribe an audio file for an elizaos agent. Returns: text. Required: agent_id, file.
- **Create a ElizaOS job** (Create). Create a one-off messaging job in elizaos. Returns: jobId, status, createdAt, expiresAt. Required: userId, content. content max 50KB; timeoutMs 1000–300000 (default 120000).
- **Get single ElizaOS job by ID** (Get). Get an elizaos messaging job by id. Returns: jobId, status, createdAt, startedAt, completedAt, result. Required: id.
- **ElizaOS jobs health** (Action). Check the health of the elizaos jobs processing system. Returns: status, queueSize, processing, avgProcessingTime, failureRate.
- **ElizaOS logs get system post** (Get). Get system logs from elizaos via POST. Returns a list of log entries including level, time, msg, agentId, and agentName.
- **ElizaOS logs clear system** (Clear). Clear all system logs in elizaos. Returns: status, message.
- **ElizaOS logs delete entry** (Delete). Delete a specific log entry for an elizaos agent. Returns an empty 204 response on success. Required: agent_id, log_id.
- **ElizaOS media upload for agent** (Upload). Upload media for an agent in elizaos. Returns the uploaded media object including id, url, mimeType, and size. Required: agent_id, file.
- **ElizaOS media upload to channel** (Upload). Upload media to a messaging channel in elizaos. Returns the uploaded media object including id, url, channelId, agentId, mimeType, and size. Required: channel_id, file.
- **ElizaOS memory create room** (Create). Create a room for an elizaos agent. Returns: id, name, agentId, createdAt, source, type, worldId, serverId, metadata. Required: agent_id, name.
- **Update a ElizaOS memory by ID** (Update). Update an elizaos memory. Returns: id, message. Required: agent_id, id.
- **ElizaOS memory delete all by agent** (Delete). Delete all memories for an elizaos agent. Returns: success, data. Required: agent_id.
- **ElizaOS memory delete all by room** (Delete). Delete all elizaos memories associated with a room. Returns an empty 204 response on success. Required: agent_id, room_id.
- **Create a ElizaOS messaging server** (Create). Create a new messaging server in elizaos. Returns the created server object with id, name, description, metadata, and createdAt. Required: name.
- **ElizaOS messaging servers add agent** (Add). Add an agent to a messaging server in elizaos. Returns: success. Required: message_server_id, agentId.
- **ElizaOS messaging servers remove agent** (Delete). Remove an agent from a messaging server in elizaos. Returns: success. Required: message_server_id, agent_id.
- **Create a ElizaOS messaging channel** (Create). Create a new messaging channel in elizaos. Returns the created channel with id, name, serverId, description, and metadata. Required: name, serverId.
- **ElizaOS messaging channels get details** (Get). Get details for a single elizaos messaging channel. Returns: id, name, serverId, description, metadata. Required: channel_id.
- **Update a ElizaOS messaging channel by ID** (Update). Update an elizaos messaging channel. Returns the updated channel with id, name, serverId, description, and metadata. Required: id.
- **Delete a ElizaOS messaging channel by ID** (Delete). Delete an elizaos messaging channel by id. Returns an empty 204 response on success. Required: id.
- **ElizaOS messaging channels add agent** (Add). Add an agent to an elizaos messaging channel. Returns: channelId, agentId, message. Required: channel_id, agentId.
- **ElizaOS messaging channels send message** (Send). Send a message to an elizaos messaging channel. Returns: id, text, userId, agentId, roomId, createdAt, metadata. Required: channel_id, author_id, content, message_server_id.
- **ElizaOS messaging channels delete message** (Delete). Delete a single message from an elizaos messaging channel. Returns an empty 204 response on success. Required: channel_id, message_id.
- **ElizaOS messaging channels clear messages** (Clear). Delete all messages from an elizaos messaging channel. Returns an empty 204 response on success. Required: channel_id.
- **ElizaOS messaging channels delete central messages by user** (Delete). Delete all messages for a user from a legacy elizaos central channel. Deprecated; use the standard channels endpoint instead. Returns: success, deleted. Required: channel_id, userId.
- **ElizaOS messaging channels get or create dm** (Get). Get or create a DM channel between two elizaos users. Returns the channel object including id, name, serverId, description, and metadata. Required: userId1, userId2.
- **ElizaOS messaging channels create central** (Create). Create a legacy elizaos central channel. Deprecated; use POST /api/messaging/channels instead. Returns the channel object including id, name, serverId, description, and metadata. Required: name, serverId.
- **ElizaOS messaging messages submit** (Action). Submit a message to the central messaging system in elizaos. Returns the stored message with id, text, userId, agentId, roomId, createdAt, and metadata. Required: channel_id, server_id, author_id, content, source_type, raw_message.
- **ElizaOS messaging messages ingest external** (Action). Ingest a message from an external platform into elizaos. Returns: success, id, text, userId, agentId, roomId, createdAt, metadata. Required: agentId, roomId, userId, text, sourceId, sourceType.
- **Create a ElizaOS session** (Create). Create a new messaging session in elizaos. Returns: sessionId, agentId, userId, createdAt, metadata, expiresAt, timeoutConfig. Required: agentId, userId.
- **Get single ElizaOS session by ID** (Get). Get an elizaos messaging session by id. Returns: sessionId, createdAt, expiresAt, error, code, details. Required: id.
- **List all ElizaOS sessions** (List). List active messaging sessions in elizaos. Returns: sessionId, agentId, userId, createdAt, lastActivity, metadata, expiresAt, timeoutConfig, renewalCount, timeRemaining, isNearExpiration.
- **ElizaOS sessions renew** (Action). Renew an elizaos messaging session before it expires. Returns the updated session with sessionId, expiresAt, renewalCount, timeRemaining, isNearExpiration, lastActivity, metadata. Required: session_id.
- **Delete a ElizaOS session by ID** (Delete). End an elizaos messaging session by id. Returns: success, message. Required: id.
- **ElizaOS sessions heartbeat** (Action). Send a heartbeat for an elizaos session to keep it alive. Returns the updated session with sessionId, agentId, expiresAt, timeoutConfig, and isNearExpiration. Required: session_id.
- **ElizaOS sessions send message** (Send). Send a message to an elizaos session. Returns the created message with id, content, authorId, sessionStatus, and isNearExpiration. Required: session_id, content.
- **ElizaOS sessions health** (Action). Check the health of the elizaos Sessions API. Returns: status, activeSessions, timestamp, expiringSoon, invalidSessions, uptime.
- ...and 32 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
