Connect OpenCode to Plaud
Set up in minutes
Choose where it runs
On your computer through your own OpenCode, or hosted in the cloud. The rest of setup adapts to your choice:
Pick what it can do in Plaud
A preset of real Plaud operations. Each one becomes a tool the agent can call, and it can't touch anything outside the list.
Connect Plaud
One sign-in. The agent acts through your account, scoped to the operations you picked.
Add your personal MCP link
The last step mints a private MCP URL for this agent and walks you through exactly this, with your real link filled in. The page flips to Connected the moment your OpenCode first calls in. opencode mcp add only saves the config. OpenCode connects when it starts — run opencode, or restart a running one.
1. Run this in your terminal
2. Choose Remote and paste your server URL
3. Choose No when asked about OAuth authentication — the link itself is the key
<your-link> is your personal server URL — setup mints it for you.
Tools OpenCode gets
Plaud
12 toolsRead the workspace belonging to the supplied US workspace token.
Read one page of members, including inactive members.
Read one page of changed recordings; retain next_checkpoint to resume.
Read recording metadata.
Read the recording's speaker-labelled transcript.
Read all generated summaries for a recording.
Get the expiring audio URL, without downloading the audio.
Read remote device binding and app history; this does not prove ownership.
Register a device/owner association in the Plaud cloud registry.
Remove the cloud binding. Also call depair(clear: true) in the device SDK to clear the local BLE binding.
Generate multipart upload URLs. Upload the raw chunks separately and keep each ETag.
Finalize previously uploaded parts. The returned download URL lasts 24 hours.
About OpenCode
Frequently asked questions
More ways to connect
More tools for OpenCode
Use Plaud with other agents
Open your OpenCode agent in one click.
NoClick runs OpenCode for you with Plaud wired in as tools. Connect your account and run.