Plaud
by Plaud
Read Plaud voice-recorder transcripts, AI notes and audio from an AI agent. Five read-only tools, verified against the published server source; get_file also returns a 24-hour audio download link. OAuth 2.0 with PKCE, and neither OAuth descriptor declares any scopes at all.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Plaud via MCP
https://mcp.plaud.ai/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Plaud Tools & Capabilities (5)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Neither OAuth document declares any scopes. The resource descriptor and the authorization server metadata both omit
scopes_supportedentirely. There is no permission the consent screen can show you and no boundary between reading a transcript and any future capability. - Consent is assigned to you, explicitly and in writing. Plaud states it does not collect consent from participants on your behalf and does not determine the legality of your recordings. Many jurisdictions require all-party consent; a wearable recorder has no participant list, no join announcement and no way for anyone else to opt out.
- The audio is reachable, not only the text.
get_filereturns a presigned download URL valid 24 hours. A transcript can be redacted before it reaches an agent; a voice recording cannot. - There is no delete, edit or correction path. No tool can remove a recording, redact a passage or fix a misattributed speaker, and Plaud's documentation confirms MCP cannot edit recordings or transcripts. Deletion runs through the app's trash, and a permanent delete without cloud sync is unrecoverable.
- Retention is open-ended. Recordings, transcripts and summaries are kept until you delete them or cancel, with unlimited storage and no published expiry. The connector inherits that horizon on every
list_filescall. - We could not read a live
tools/listresponse. The endpoint returned HTTP 401 to an anonymous request. The tool names, schemas and safety annotations here come from the published source of@plaud-ai/mcp0.3.9 — strong evidence, and still not the running server's own reply. - Cloud sync is mandatory and is a second decision. MCP reads only synced recordings, so connecting it means opting a device-local library into Plaud's cloud.
- Plaud's own MCP FAQ contains an error worth knowing about. It states Plaud MCP "only works with AI assistants running on your own computer" and that your login stays local. That is true of the npx install; it is not true of the Claude Web and ChatGPT Web route the same article documents, which runs through the hosted server. Plaud's developer docs are the accurate source here, noting that on HTTP clients your data passes through Plaud's US-hosted MCP server, processed in transit only.
- A published rate limit for MCP does not exist. Plaud documents no request ceiling for this server anywhere we could find.
- The 7-day retention figure in Plaud's developer docs is not this product. It applies to the Plaud Embedded transcription API for third-party builders. Consumer recordings behind this connector follow the account-lifetime policy above.
Frequently asked questions
Not reliably, and Plaud says the duty is yours. Its help centre states you are responsible for informing all participants and obtaining any legally required consent, and that Plaud does not collect consent on your behalf. The NotePin S shows a red LED that cannot be turned off, but an LED on a worn pin is notice only if someone looks at it.
Transcripts, AI notes and the audio itself. The five tools return recording metadata, the timestamped transcript with speaker attribution, the AI summary with action items and key topics, and a temporary audio download URL. Plaud's help centre confirms the assistant gets a download link valid for 24 hours alongside the transcript and summary.
No. All five tools carry readOnlyHint true and destructiveHint false in the published server source. Plaud's own export skill states plainly that Plaud MCP does not expose a push tool, and its documentation lists what the connector cannot do: it cannot record audio and it cannot edit recordings or transcripts. There is no delete path.
None are declared. The server's RFC 9728 protected-resource descriptor and its authorization-server metadata were both read on 2026-08-23 and neither document carries a scopes_supported field. Nothing at the consent screen narrows the grant, so authorizing the connector authorizes the whole tool surface as one unit, now and as it grows.
Until you delete them or close the account. Plaud's security article states recordings, transcripts and summaries are retained until the user manually deletes them or cancels their subscription, with no time-based expiry. Cloud storage is described as unlimited, so a broad list_files call reaches every synced recording you have ever made.
Five on the remote server, and Plaud's own table lists seven. The two extras, login and logout, are registered only by the local stdio entry point in the published npm package. The hosted endpoint this page describes registers the same five the directory lists, so the two lists agree once the transports are separated.
A Plaud account with Private Cloud Sync switched on. Plaud states that MCP works by giving your assistant access to your synced recordings, so cloud sync must be enabled, and that Plaud MCP is currently free for all active accounts. Terminal installs additionally need Node.js 20 or later.
Yes, and that is the documented reason to use it. Plaud's help centre states its OAuth API deliberately returns only your 20 most recent recordings, and directs anyone needing full history to MCP or the CLI, neither of which is subject to that cap. MCP is the widest read path Plaud offers an individual user.
Sources
- Plaud MCP developer documentation (retrieved 2026-08-23, as Markdown via the
.mdroute). That host'srobots.txtcarriesContent-Signal: ai-train=yes, search=yes, ai-input=yes— AI synthesis expressly permitted. · retrieved 2026-08-23 - Plaud developer documentation index,
llms.txt(retrieved 2026-08-23) · retrieved 2026-08-23 - Plaud CLI documentation — · MCP & CLI changelog (retrieved 2026-08-23) · retrieved 2026-08-23
@plaud-ai/mcp0.3.9, published 2026-08-20 — registry metadata and tarball read from (thenpmjs.comweb page and itsrobots.txtboth sit behind a Cloudflare challenge that returns 403 to our client, so the registry API was used instead). Tool names, descriptions, input schemas, safety annotations and the stdio/HTTP split were read from the package's owndistbundle and its bundledskills/directory (retrieved 2026-08-23). · retrieved 2026-08-20- Plaud help centre, Plaud MCP (retrieved 2026-08-23, via the Zendesk
help_centerJSON API after the HTML returned 403 to our client) · retrieved 2026-08-23 - Plaud help centre, recording-consent cluster: "Do I need to obtain consent before recording with Plaud devices or Apps?" — · "Does Plaud obtain recording consent on my behalf?" — · "How can I properly notify others before recording?" — · "What happens if I record without obtaining consent?" (all retrieved 2026-08-23) · retrieved 2026-08-23
- Plaud help centre, "How can I get API access to my Plaud data?" — · "Why doesn't the Plaud API return all of my recordings?" (retrieved 2026-08-23) · retrieved 2026-08-23
- Plaud help centre, "Plaud's security and compliance" (retention and residency) — · "How your data is used in AI processing" (retrieved 2026-08-23) · retrieved 2026-08-23
- Plaud help centre, Team workspace visibility — · Private Cloud Sync — · Indicator light — · Automatic Recording — · Delete Audio (retrieved 2026-08-23) · retrieved 2026-08-23
- Plaud Trust Center (retrieved 2026-08-23;
/pages/trust-centeris a 301 to this URL) · retrieved 2026-08-23 - Plaud privacy policy, last updated 16 June 2026 (retrieved 2026-08-23) · retrieved 2026-08-23
- Live OAuth posture check: an anonymous initialize returned HTTP 401 with a
www-authenticateBearer challenge naminghttps://mcp.plaud.ai/.well-known/oauth-protected-resource/mcp; that descriptor and the authorization server metadata athttps://mcp.plaud.ai/.well-known/oauth-authorization-serverwere both read, and a nonsense control path under the same prefix returned 404, confirming no interpolating catch-all (2026-08-23) · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Plaud developer support — <mailto:dev-support@plaud.ai> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Plaud
- Tools
- 5
- Domain
- mcp.plaud.ai
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.