Circleback MCP connector
Connect Circleback to Elaichi and Claude, ChatGPT, Cursor, or the Elaichi Agent can search your meetings, read transcripts and notes, and manage action items, each person inside their own Circleback access.
-
How it connects. Connects over OAuth. 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.
21 tools
How to connect
How to connect Circleback to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Circleback once
-
Open Connections, choose Add connection, and pick Circleback.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Circleback. Circleback's own window opens. Whoever approves it decides what this connection can reach.
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.
Circleback 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.
Circleback 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.
Circleback 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 Circleback 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 Circleback through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Catch up before the next call
Ask what was promised on the last three Circleback calls with an account and get the action items, open questions and who owns each, before you dial in.
-
Customer Success
Turn a renewal call into follow-ups
After a customer meeting, have the agent read the transcript, create the action items that were agreed, and share the meeting with the account team.
-
Support
Find where a customer raised an issue
Search transcripts for the moment a customer first mentioned a bug or a billing problem, then pull the matching support article to send back.
-
Product
Pull feedback across customer interviews
Search a month of discovery calls for mentions of a feature, tag the relevant meetings, and get the recurring requests summarized in one place.
-
Leadership
Review the week's decisions in minutes
Ask for every decision and open action item from this week's leadership and team meetings, grouped by owner, without opening each recording.
-
Recruiting
Keep interview notes and next steps tidy
After each interview, update the meeting notes, create the action items for the panel, and tag the meeting with the role so the loop stays organized.
Try asking
- “What action items came out of yesterday's Acme renewal call?”
- “Summarize this week's customer onboarding meetings for the team.”
- “Find every transcript where someone mentioned pricing this month.”
Compare
Elaichi vs Zapier MCP vs Composio for Circleback
All three can connect Circleback 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 Circleback tools | Allow or restrict single Circleback 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 Circleback 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
Circleback tools for your AI agents
21 tools are ready to call through Elaichi's MCP endpoint the moment you connect Circleback, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Circleback builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Circleback gets you
6 screens from the product, each doing one job for your Circleback account.
The agent
Ask about any meeting and get the answer.
Search Circleback meetings, transcripts and action items in plain language from live records.
- meetings
- transcripts
- action items
- calendar events
Ask Elaichi to work across your apps.
What action items came out of yesterday's Acme renewal call?
Summarize this week's customer onboarding meetings for the team.
Find every transcript where someone mentioned pricing this month.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint reaches Circleback from every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
21 Circleback tools, no code to write.
Meetings, transcripts, action items, calendar events and tags, covered without custom code.
- Search meetings
- Read meetings
- Update meeting
- Update calendar event
ElaichiToolsToolboxes
Every team gets its own Circleback toolbox.
Sales sees meetings and action items, Support sees transcripts, each scoped to its team.
- Sales
- Customer Success
- Support
- Product
ElaichiToolboxesShared connections
Share a Circleback connection, not a password.
One person connects, teammates work through it, and nobody else sees a credential.
- Sales EMEA
- Customer Success
- Support
- Product
ElaichiConnectionsAudit log
Know who read which Circleback transcript.
Every call lands in an append-only log with who, what, when and which meeting.
- 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 fires and the digest goes out.
Meetings are fetched, grouped, drafted into a digest, approved by a person, then posted to Circleback.
Circleback digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch meetings
Circleback
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
Circleback
Queued
Collections and dashboards
Circleback numbers, computed, nobody has to ask.
Four metrics and 14 days of meetings by team, refreshed on schedule with no model involved.
Circleback health
Refreshed 4 minutes ago · every 15 minutes · from the meetings collection
Meetings
1,284 ↓ 12%
Transcripts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Meetings created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Customer Success 27%
Support 21%
Product 18%
FAQ
Frequently asked questions
How do I connect Circleback to Claude?
Connect Circleback in Elaichi first: pick Circleback from the catalog and sign in with your Circleback account over OAuth. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in to Elaichi and Circleback is ready to ask about.
Does Circleback work with ChatGPT and Cursor as well as Claude?
Yes. Once Circleback 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 Circleback once and every client you use picks it up.
What can an AI agent actually do with my Circleback data?
With Circleback connected, an agent can find meetings, read their notes and transcripts, search for what was said about a topic, and create, update or close action items. It can also update meeting details and calendar events, share a meeting with a colleague, manage tags, and look up the people and companies who were on a call. Short, concrete asks such as "open action items from yesterday's Acme call" work better than long sentences.
Does connecting Circleback give the AI every meeting in the workspace?
No. Access follows the person who signed in, so an agent only sees the Circleback meetings, transcripts and action items that person can already open. Elaichi can narrow that further, for example to searching and reading only, but it can never widen access beyond what Circleback itself allows.
Can I stop an agent from deleting or changing things in Circleback?
Yes. Restrictions in Elaichi apply per action, so you can allow searching and reading Circleback meetings while blocking deleting action items or tags, or editing meetings at all. A restricted action is never advertised to Claude, ChatGPT or Cursor, so no prompt, however it is worded, can reach it.
What happens to a Circleback connection when someone leaves?
Offboarding a person in Elaichi ends their access to Circleback through every client at once. A Circleback connection they shared keeps working for everyone else on the team. If you want it gone entirely, disconnecting Circleback once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the Circleback MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Circleback 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 Circleback?
Yes. Both let Claude, ChatGPT or Cursor use Circleback. 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 Circleback call.
How is Elaichi different from Composio for Circleback?
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 Circleback: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Circleback 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.