Bring Voice Recording
to Claude Desktop
Learn how to connect Plaud to Claude Desktop and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
What is the Plaud MCP Server?
Empower your AI agent to orchestrate your entire voice-to-intelligence ecosystem with Plaud, the AI voice recorder. By connecting Plaud to your agent, you transform complex recording management into a natural conversation. Your agent can instantly list your files, retrieve AI-generated transcripts, and audit meeting summaries without you ever touching a dashboard. Whether you are capturing client meetings, lectures, or personal notes, your agent acts as a real-time intelligence assistant, ensuring your spoken data is always accessible and organized.
What you can do
- Recording Auditing — List all recordings in your account and retrieve detailed metadata for each, including creation dates.
- Intelligence Extraction — Query full transcripts and AI summaries for any recording instantly to capture key insights.
- Organization Management — List all folders and tags to keep your recording library structured and easy to browse.
- Data Governance — Update file names and autonomously delete recordings when they are no longer needed.
- Asset Access — Retrieve secure download URLs for your audio files to maintain local backups or share recordings.
How it works
1. Subscribe to this server
2. Enter your Plaud Access Token and API Domain
3. Start managing your voice data through Claude, Cursor, or any MCP-compatible client
Who is this for?
- Professionals — monitor meeting recordings and retrieve summaries straight from your workflow.
- Students — verify if lecture transcripts have been correctly generated and organized by the agent.
- Content Creators — perform rapid audits of voice notes and extract content ideas without manual dashboard logins.
- Operations Leads — automate recording querying to orchestrate cross-functional team intelligence smoothly.
Built-in capabilities (10)
Delete a Plaud recording
Get MP3 download URL for a recording
Get details for a specific recording
Get Plaud account details
Get AI summary for a recording
Get transcription for a recording
List all Plaud recordings
List all recording folders
List all recording tags
Update recording metadata
Why Claude Desktop?
Claude Desktop is the definitive way to connect Plaud to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Plaud in Claude Desktop
Plaud and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Plaud to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Plaud in Claude Desktop
The Plaud MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Plaud for Claude Desktop
Every tool call from Claude Desktop to the Plaud MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Plaud Access Token?
Log in to web.plaud.ai, open DevTools (F12), go to Application > Local Storage, and look for tokenstr. Copy and paste it into the field below.
What is the Plaud API Domain?
It is the base URL for the Plaud API (e.g., https://api-euc1.plaud.ai). You can find it in your browser's Local Storage under plaud_user_api_domain.
Can the agent retrieve full AI summaries?
Yes. Use the get_summary tool with the File ID. Your agent will fetch the structured AI summary, including key points and action items.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.