Plaud MCP Server

MCP server for Plaud transcripts via CDP proxy through the running Plaud Desktop app.

How It Works

Claude Code → MCP Server → CDP (WebSocket) → Plaud Desktop → Plaud API

The MCP connects to the running Plaud Desktop Electron app via Chrome DevTools Protocol:

1. Sends SIGUSR1 to the Plaud Desktop process to enable Node.js inspector (port 9229)

2. Connects via WebSocket to the inspector

3. Executes API calls through the app's own authenticated $fetch function

4. Returns results back through MCP tools

No token extraction, no cookies, no API keys. Uses the app's live authenticated session directly.

Related MCP server: Plaud MCP Server

Prerequisites

1. Plaud Desktop - installed and signed in

2. Python 3.10+

3. uv (recommended)

Installation

# Install as a CLI tool (recommended)
uv tool install "plaud-mcp @ git+https://github.com/davidlinjiahao/plaud-mcp"

# Or install from local source
uv tool install --force "plaud-mcp @ ."

Configuration

Add to ~/.claude.json:

{
  "mcpServers": {
    "plaud": {
      "command": "${HOME}/.local/bin/plaud-mcp",
      "args": [],
      "env": {}
    }
  }
}

No API keys or tokens needed. Just ensure Plaud Desktop is running.

MCP Tools

Troubleshooting

"Plaud Desktop is not running"

Launch the Plaud Desktop app and sign in.

"Could not enable inspector"

The SIGUSR1 signal may have failed. Ensure Plaud Desktop is the main process, not a helper.

Search is slow

search_transcripts fetches and searches client-side. Reduce the days parameter.

Why CDP?

Plaud's API validates auth at the Chromium network stack level - tokens extracted from LevelDB don't work with standard HTTP clients (httpx, curl, curl_cffi with Chrome impersonation all return 401). The CDP approach bypasses this entirely by executing requests through the app's own authenticated context.

Development

uv venv && source .venv/bin/activate
uv pip install -e ".[dev]"
ruff check src/ && pyright src/