Connect your AI Agents to Plaud in minutes

What is a Plaud MCP?

It's an MCP server that connects your agents to a Plaud account through tools. Your agents can invoke them to search recordings, read speaker-labeled transcripts, pull AI-generated summaries, export documents from a recording, and more.

Plaud offers an official MCP server, but you can also use one from a third-party platform, like Merge Agent Handler.

How can I use the Plaud MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

• Post-call CRM updates: after a sales call is recorded in Plaud, an agent can pull the transcript, extract next steps and objections, and log them against the matching opportunity in your CRM

• Meeting summary distribution: an agent can take a recording's summary and send a recap with action items to attendees over email or Slack

• Research synthesis across calls: an agent can search a set of user-interview recordings for a theme and combine the relevant excerpts into a single findings document

• Transcript lookups on demand: a teammate can ask their AI what was decided in a specific meeting, and the agent retrieves the transcript and answers from it

What are popular tools for Plaud's MCP server?

Here are some of the most commonly used tools:

• list_recordings: returns recordings filtered by date or label. Useful for agents that need to find the right session before acting on it

• get_transcript: returns the full speaker-labeled transcript for a recording. Call this when an agent needs the verbatim contents of a conversation

• get_summary: returns the AI-generated summary of a recording. Use this when an agent needs the gist rather than the full transcript

• search_recordings: searches across recordings for a keyword or topic. Good for workflows that pull every conversation touching a given subject

• export_document: generates a formatted document from a recording, such as meeting notes. Helpful when an agent produces a shareable artifact from a call

• get_recording: returns metadata and audio details for a single recording. Useful for agents that need the context around a session before processing it

What makes Merge Agent Handler's Plaud MCP server better than alternative Plaud MCP servers?

Choosing Merge Agent Handler's Plaud MCP server over a self-built or community option comes down to a few things:

• Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Plaud, this means transcript contents and the personal information discussed in a meeting can be redacted before they ever reach the agent

• Managed authentication and credentials: Merge stores and refreshes Plaud credentials on your behalf. You never expose raw API keys or OAuth tokens to an agent or handle token rotation yourself

• Real-time observability and audit trail: Every tool call made against Plaud is logged with timestamp, tool name, input parameters, and response metadata. You can see exactly which recordings and transcripts an agent accessed without building logging yourself

• Tool Packs and controlled access: Tool Packs let you bundle specific Plaud tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's Plaud MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account.

2. Install the Merge CLI by running pipx install merge-api, then run merge configure to link the CLI to your Merge account and merge login to authenticate your session.

3. Register the Agent Handler MCP server with Claude Code by running claude mcp add --transport http agent-handler https://ah-api.merge.dev/mcp, then open Claude Code and run /mcp to confirm agent-handler appears with a connected status.

4. Select agent-handler from the MCP list. This opens a browser window where you select which integrations to authenticate. Choose Plaud and complete the auth flow. Merge stores and manages the credentials going forward.

5. Open a Claude Code session and start querying Plaud data directly. The first time you use a Plaud tool, a Magic Link may appear to complete connector authentication.

If you want to connect Merge Agent Handler's Plaud MCP with internal or customer-facing agentic products, you can follow the steps in our docs.

Can employees use Merge to connect their AI tools to Plaud?

Yes, Merge for Workforce lets your employees connect Claude, ChatGPT, Microsoft Copilot, Cursor, and other MCP-compatible AI tools to Plaud without bypassing IT governance.

Instead of setting up direct connections with personal credentials that IT can't monitor or revoke, each employee authenticates through Merge and gets individual credentials tied to their identity. A teammate can ask their AI to pull a call transcript, summarize a meeting, or draft notes from a recording, all within the permissions IT has defined.

IT also provisions access by role or group via SCIM. A sales rep, for example, gets Plaud access to pull call transcripts, Salesforce to log the conversation, and Gmail to send the follow-up; while a product manager gets Plaud access to review user-interview recordings, Linear to file feature requests, and Notion to write up the findings.

Every tool call an employee's AI makes to Plaud is also inspected against your DLP rules and logged to a searchable audit trail, giving security teams full visibility into what data was accessed and by whom.