Circleback MCP connector
Connect Circleback to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, or the Elaichi Agent can search your meetings, read transcripts and notes, and manage action items, each person inside their own Circleback access.
- Connects over OAuth
- Free 14-day trial
- No credit card
What action items came out of yesterday's Acme renewal call?
Working in Circleback with Elaichi
-
Search meetings
-
Search transcripts
-
Get transcripts for meetings
How to connect Circleback to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 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.
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. 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.
Circleback 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 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.
What teams do with Circleback through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Circleback is logged.
-
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.”
What connecting Circleback gets you
6 screens from Elaichi, each doing one job for your Circleback account.
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, Cursor or Microsoft Copilot
The agent
Ask about any meeting and get the answer.
Search Circleback meetings, transcripts and action items in plain language from live records.
Copy the endpoint
AI apps
One endpoint reaches Circleback from every client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Tool catalog
21 Circleback tools, no code to write.
Meetings, transcripts, action items, calendar events and tags, covered without custom code.
Toolboxes
Every team gets its own Circleback toolbox.
Sales sees meetings and action items, Support sees transcripts, each scoped to its team.
Shared connections
Share a Circleback connection, not a password.
One person connects, teammates work through it, and nobody else sees a credential.
Audit log
Know who read which Circleback transcript.
Every call lands in an append-only log with who, what, when and which meeting.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
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 Jake Morgan
Approve Deny -
Post the digest
Circleback
Queued
Workflows
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 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%
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.
Why connect Circleback's MCP server through Elaichi
Circleback builds and runs this MCP server. Elaichi sits in front of it, so Circleback's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Circleback's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Circleback's tools at the same Elaichi address as every other connected app. Nobody adds Circleback's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Circleback sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Circleback's server. By default, a tool Circleback does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Circleback
Circleback builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Circleback team.
For IT and engineering
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 | 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.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting deleting action items or tags, or editing meetings at all. 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 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, Microsoft Copilot 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, 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 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 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