Bring Voice Recording
to Cursor
Learn how to connect Plaud to Cursor 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 Cursor?
Cursor's Agent mode turns Plaud into an in-editor superpower. Ask Cursor to generate code using live data from Plaud and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Plaud in Cursor
Plaud and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Plaud to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.