Plaud MCP connector
The Plaud connector brings your Plaud recordings, notes and transcripts to Claude, ChatGPT, Cursor and the Elaichi Agent, so you can ask about any conversation you recorded and get answers drawn from the transcript itself.
-
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.
5 tools
How to connect
How to connect Plaud to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Plaud once
-
Open Connections, choose Add connection, and pick Plaud.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Plaud. Plaud'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.
Plaud 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.
Plaud 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.
Plaud 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 Plaud 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 Plaud through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Catch the deal up after a call
Ask for the transcript of this morning's call with a prospect and get the objections, the pricing questions and the next steps pulled out before you update the deal.
-
Support
Find what the customer actually said
Search your Plaud files for the escalation call and have the agent quote the exact wording of the complaint, so the handoff note is accurate.
-
Customer success
Prepare for a renewal in minutes
Pull every recorded conversation with an account this quarter and ask for the recurring themes, the promises made and the open risks.
-
People
Turn interview recordings into structured feedback
Ask for the transcript of each candidate interview and get the answers to the scorecard questions laid out side by side.
-
Product
Mine customer interviews for patterns
Point the agent at a set of research call notes and ask which feature requests came up most and who raised them.
-
Leadership
Get the gist of a meeting you missed
Ask for the notes and transcript from yesterday's leadership meeting and get the decisions, the owners and the deadlines in a short brief.
Try asking
- “Summarize yesterday's call with Acme into three follow-ups”
- “Find the transcript where the customer asked about pricing”
- “Pull the action items from Tuesday's leadership meeting notes”
Native MCP
Why connect Plaud's MCP server through Elaichi
Plaud builds and runs this MCP server. Elaichi sits in front of it, so Plaud'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 Plaud's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT and Cursor reach Plaud's tools at https://api.elaichi.ai/mcp, the same address as every other connected app. Nobody adds Plaud'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 Plaud 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 Plaud's server. By default, a tool Plaud does not mark read-only or non-destructive counts as destructive, and over MCP it needs the "Delete data and remove access" 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 Plaud
Plaud builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Plaud team.
Compare
Elaichi vs Zapier MCP vs Composio for Plaud
All three can connect Plaud 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 Plaud tools | Allow or restrict single Plaud 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 Plaud 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
Plaud tools for your AI agents
5 tools are ready to call through Elaichi's MCP endpoint the moment you connect Plaud, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Plaud builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Plaud gets you
6 screens from the product, each doing one job for your Plaud account.
The agent
Ask about any call you recorded in Plaud.
Summaries, quotes and action items come straight from the transcript, not from memory.
- files
- notes
- transcripts
- users
Ask Elaichi to work across your apps.
Summarize yesterday's call with Acme into three follow-ups
Find the transcript where the customer asked about pricing
Pull the action items from Tuesday's leadership meeting notes
Also runs in Claude, ChatGPT or Cursor
MCP clients
Plaud works in every AI client you already use.
Claude, ChatGPT and Cursor read Plaud transcripts through one endpoint, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
5 Plaud tools, ready without writing code.
Files, notes and transcripts are covered the moment you sign in.
- Get current user
- List files
- Get file
- Get note
ElaichiToolsToolboxes
Each team gets its own Plaud toolbox.
Sales reads call transcripts, People reads interview notes, each scoped to its own team.
- Sales
- Support
- Customer success
- People
ElaichiToolboxesShared connections
Share Plaud without sharing a password.
One person connects, the whole team reads transcripts, nobody else touches a credential.
- Sales EMEA
- Support
- Customer success
- Recruiting
ElaichiConnectionsAudit log
Every Plaud transcript read is on the record.
Who opened which recording, when, and from which client, in an append-only log.
- 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 turns Plaud recordings into a digest.
Transcripts are fetched, grouped and drafted into a digest, then you approve before it posts.
Plaud digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch files
Plaud
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
Plaud
Queued
Collections and dashboards
Plaud recording numbers, computed on a schedule.
Files recorded per day and per team, counted from Plaud with no model involved.
Plaud health
Refreshed 4 minutes ago · every 15 minutes · from the files collection
Files
1,284 ↓ 12%
Notes
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Files created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Support 27%
Customer success 21%
Recruiting 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Plaud to Claude?
Connect Plaud in Elaichi first: you sign in to your Plaud account with OAuth, the same way you would sign in to Plaud on the web, and there is no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in to Elaichi once, and from then on it can read your Plaud recordings, notes and transcripts as you.
Does Plaud work with ChatGPT and Cursor as well as Claude?
Yes. Once Plaud 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 Plaud once and add the endpoint to whichever clients your team uses.
What can an AI agent actually do with my Plaud data?
With Plaud connected, an agent can list your recorded files, open a specific recording, read the notes Plaud produced for it and read the full transcript. That means you can ask for a summary of a call, the exact words a customer used, or the action items from a meeting, and the answer comes from the transcript rather than from memory. Short, specific asks such as naming the meeting or the day work better than long instructions.
Does connecting Plaud give the AI access to every recording in my account?
An agent sees the Plaud recordings the person who signed in can see, and nothing more. Elaichi can narrow that further, for example limiting a team to reading transcripts only, but it can never widen access beyond what your Plaud account already allows.
Can I stop an agent from deleting or changing things in Plaud?
The Plaud connector only reads: it lists files and returns notes and transcripts, and it has no way to delete or edit a recording. Elaichi restrictions also apply per action, so if you want a team to read notes but not full transcripts, that action is left out of the tool list the AI client sees and cannot be called, whatever the prompt says.
What happens to a Plaud connection when someone leaves?
When you offboard someone in Elaichi, their access to Plaud through every AI client ends at once. A Plaud connection they shared keeps working for everyone else on the team. If you want the connector gone entirely, disconnecting Plaud once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the Plaud MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Plaud 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 Plaud?
Yes. Both let Claude, ChatGPT or Cursor use Plaud. 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 Plaud call.
How is Elaichi different from Composio for Plaud?
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 Plaud: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Plaud 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.