Chatvolt MCP connector
The Chatvolt connector brings your Chatvolt agents, conversations, messages, blacklists and dispatches into Claude, ChatGPT, Cursor and any MCP client, so your team can review and work chats in plain language inside their own Chatvolt 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.
113 tools
How to connect
How to connect Chatvolt to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Chatvolt once
-
Open Connections, choose Add connection, and pick Chatvolt.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Chatvolt API key. One person generates a token in Chatvolt 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.
Chatvolt 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.
Chatvolt 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.
Chatvolt 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 Chatvolt 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 Chatvolt through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Triage the conversation queue each morning
Ask for the open Chatvolt conversations, sort them by priority, and assign the urgent ones to the right person before the day starts.
-
Support
Take over a chat from the bot
When a customer is stuck, switch the AI off for that Chatvolt conversation, assign it to yourself, and send the reply as a human.
-
Sales
Follow up leads from Chatvolt chats
Pull the recent conversations that mention pricing or a demo, read what the visitor asked, and send a follow-up message without opening Chatvolt.
-
Operations
Tune agent settings without the admin screen
Update a Chatvolt agent's name, instructions or behavior by describing the change, and check the result by asking for the agent's current settings.
-
Marketing
Send a dispatch to a segment
Create a Chatvolt dispatch to reach a group of contacts with a campaign message, then watch which conversations come back.
-
Customer success
Keep account details on the conversation
Record plan, region or renewal date as variables on a Chatvolt conversation so the agent and your teammates see the context on the next message.
Try asking
- “Which Chatvolt agents handled the most conversations this week?”
- “Assign the high priority Chatvolt conversations to the support queue.”
- “List blacklist entries added to our billing agent.”
Compare
Elaichi vs Zapier MCP vs Composio for Chatvolt
All three can connect Chatvolt 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 Chatvolt tools | Allow or restrict single Chatvolt 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 Chatvolt 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
Chatvolt tools for your AI agents
113 tools are ready to call through Elaichi's MCP endpoint the moment you connect Chatvolt, 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 Chatvolt gets you
6 screens from the product, each doing one job for your Chatvolt account.
The agent
Ask about agents and conversations in plain language.
The agent screen answers from live Chatvolt agents, conversations and blacklists.
- agents
- conversations
- blacklists
- assignments
Ask Elaichi to work across your apps.
Which Chatvolt agents handled the most conversations this week?
Assign the high priority Chatvolt conversations to the support queue.
List blacklist entries added to our billing agent.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Chatvolt here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
113 Chatvolt tools are ready to call.
Agents, conversations, blacklists and their methods are listed, with no custom code.
- Chatvolt agents query
- Get single Chatvolt agent by ID
- Create a Chatvolt agent
- Update a Chatvolt agent by ID
ElaichiToolsToolboxes
Every team gets its own Chatvolt toolbox.
Support, sales and ops each see a curated set of Chatvolt tools.
- Support
- Sales
- AI Ops
- Trust and Safety
ElaichiToolboxesShared connections
Teammates use Chatvolt accounts without seeing credentials.
The connections table shows who connected each account and which teams share it.
- Support EMEA
- Sales US
- AI Ops
- Trust and Safety
ElaichiConnectionsAudit log
Every Chatvolt call is written down.
When, who, what happened, type and resource for each agent and conversation call.
- 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 Chatvolt conversation digest.
Six steps fetch conversations, group them, draft a digest, get approval, post back.
Chatvolt digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch agents
Chatvolt
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
Chatvolt
Queued
Collections and dashboards
Chatvolt agent health, counted on a schedule.
Four metrics, fourteen days of conversations created, and a breakdown by team.
Chatvolt health
Refreshed 4 minutes ago · every 15 minutes · from the agents collection
Agents
1,284 ↓ 12%
Conversations
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Agents created
Last 14 days
By team
Share of activity
Support EMEA 34%
Sales US 27%
AI Ops 21%
Trust and Safety 18%
FAQ
Frequently asked questions
How do I connect Chatvolt to Claude?
Connecting Chatvolt to Claude takes two steps. First, open Elaichi, choose Chatvolt from the catalog, and paste your Chatvolt API key when asked. Then in Claude go to Customize, then Connectors, then Add, and enter https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate.
Does Chatvolt work with ChatGPT and Cursor as well as Claude?
Yes. Once Chatvolt 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 Chatvolt once and every client sees it.
What can an AI agent actually do with my Chatvolt data?
With Chatvolt connected, an AI agent can list your conversations, read the messages in any of them, set a conversation's status or priority, assign it to a teammate, switch the AI on or off for it, and send or log a message. It can also look up, create, update or remove Chatvolt agents and their blacklists, manage the variables stored on a conversation, and create a dispatch. Short, concrete asks such as "show me open Chatvolt conversations from today" work better than long paragraphs.
Does connecting Chatvolt give the AI access to every agent and conversation?
No. Access to Chatvolt follows the person who signed in, so the AI sees only the agents and conversations that person's Chatvolt account can already reach. Elaichi can narrow that further, for example to reading conversations but not deleting them, and it never widens it beyond what the person already has in Chatvolt.
Can I stop an agent from deleting or changing things in Chatvolt?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Chatvolt conversations and sending messages while blocking deleting conversations, deleting agents or clearing variables. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.
What happens to a Chatvolt connection when someone leaves?
When you offboard a person in Elaichi, their access to Chatvolt through every client ends at once. A shared Chatvolt connection keeps working for everyone else on the team. If you want to remove Chatvolt entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the Chatvolt MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Chatvolt 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 Chatvolt?
Yes. Both let Claude, ChatGPT or Cursor use Chatvolt. 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 Chatvolt call.
How is Elaichi different from Composio for Chatvolt?
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 Chatvolt: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Chatvolt 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.