@seameet/mcp

The SeaMeet MCP server — let AI agents record, transcribe, and mine your meetings. One install works whether or not you have the desktop app, in Claude Code, Claude Desktop, Codex, Antigravity, Cursor, OpenCode, GitHub Copilot CLI, Windsurf, and any MCP client.

It picks the richest available backend automatically and exposes the union of both:

• Desktop mode — when the SeaMeet desktop app is running, agents get the full recorder toolset (start/stop recordings, screenshots, live transcript, AI artifacts, search). No auth; nothing leaves your machine.
• Cloud mode — when the app isn't there, agents read your synced library (recordings, transcripts, summaries) and manage webhooks over the network. Authorized by logging into the web app — no key copy/paste, works on a headless terminal.

`tools/list` returns the superset of whatever's available; call `seameet_status` any time to see the current mode(s).

What you can do

🎙️ Record & capture *(desktop mode)*

• Start a recording — microphone, screen, or screen + system audio — `seameet_start_recording`
• Stop — `seameet_stop_recording` · pause/resume audio-only — `seameet_pause_recording` / `seameet_resume_recording`
• Check recording status — `seameet_recording_status` · read the live transcript mid-recording — `seameet_get_live_transcript`
• Take a screenshot through SeaMeet — `seameet_take_screenshot`

📚 Work with recordings *(desktop = local files · cloud = synced library)*

• List recordings & screenshots — `seameet_list_recordings` · browse files in the save directory — `seameet_list_files` · app settings — `seameet_get_settings`
• Read generated artifacts (summary, transcript, SRT, chapters, action items, key decisions, screenshot OCR/description) — `seameet_get_artifact`
• Search across artifact text — `seameet_search_text`
• Fetch a recording's asset-bundle manifest — `seameet_get_asset_bundle`
• Rename a file — `seameet_rename_file` · save a new artifact — `seameet_save_artifact` · regenerate a summary from a template — `seameet_regenerate_summary` · list templates — `seameet_list_templates`

☁️ Cloud library *(cloud mode)*

• List recent synced recordings — `seameet_list_recent_recordings` · fetch summary / transcript / chapters / action items / key decisions — `seameet_get_recording`
• Get a temporary media stream/download URL — `seameet_get_media_url`
• Check storage usage — `seameet_get_usage`
• Manage outbound webhooks (signed deliveries on `ai.ready` / `recording.synced`) — `seameet_create_webhook` · `seameet_list_webhooks` · `seameet_update_webhook` · `seameet_delete_webhook`

🔌 Connection *(any mode)*

• Which modes are connected — `seameet_status` · disconnect cloud / switch accounts — `seameet_logout`

That's 17 desktop tools + 8 cloud tools (fetched live, so new releases appear automatically). A tool the current backend can't serve returns a clear, structured error instead of failing silently.

Install

Every client runs the same command — `npx -y @seameet/mcp` — only the config format differs. Full per-tool recipes: **INSTALL.md** (mirrored at app.seameet.ai/mcp/install.md).

Let your agent do it — already inside a coding agent? Paste:

> Install the SeaMeet MCP server — fetch

> `https://raw.githubusercontent.com/seameet-ai/seameet-mcp/main/INSTALL.md`, apply the section for

> whichever tool you're running in, and tell me how to reload.

Or pick your tool:

The generic block, accepted by most MCP clients:

{
  "mcpServers": {
    "seameet": { "command": "npx", "args": ["-y", "@seameet/mcp"] }
  }
}

Requirements

• Node.js ≥ 18.
• For desktop mode: the SeaMeet desktop app installed and running — `brew install --cask seameet-ai/tap/seameet` (macOS) or `winget install seameet` (Windows). Needs v3.2.0+; an older running app reports `app_outdated`.
• Cloud mode is opt-in and needs no app — the first cloud tool call starts a one-time authorization (below).

Cloud authorization (one-time, no key copy/paste)

Cloud mode never activates unless you provide `SEAMEET_API_KEY` or complete the device flow. On the first cloud tool call with no key, the agent shows a short code + `https://app.seameet.ai/link`; you open it (signed in), click Authorize, and a read+write key is minted and cached at `~/.seameet/credentials.json`. Silent thereafter; revoke any time under API keys on your account. To disconnect or switch accounts, call `seameet_logout` (or `rm ~/.seameet/credentials.json`).

Claude Desktop one-click bundle

`manifest.json` is an MCPB bundle manifest, so the server ships as a one-click Claude Desktop extension:

npm install && npm run build:mcpb   # → dist/seameet.mcpb

Install via Settings → Extensions → Advanced → Install extension… and pick `dist/seameet.mcpb`. Claude Desktop runs it with its own Node.js — no terminal needed. (The desktop app still needs to be installed + running for desktop mode.)

Claude Code plugin (adds a `/seameet` skill)

This repo doubles as a Claude Code plugin marketplace. The plugin registers the MCP server and a `/seameet` skill that teaches the core workflows (record + transcribe, capture a bug report, mine meetings for action items):

claude plugin marketplace add seameet-ai/seameet-mcp
claude plugin install seameet@seameet

Try it

Just ask in plain language — the agent picks the right tool (and the right backend). A few starters:

> Record my screen for 2 minutes, then give me the transcript.

> What were the action items from my last meeting?

> Take a screenshot and describe what's on it.

Desktop mode — a full recording session (app running)

• "What are my SeaMeet settings — where does it save recordings?"
• "List my summary templates."
• "List my local recordings." · "List the files in my SeaMeet save folder."
• "What's my current recording status?"
• "Start recording my microphone." *(or: "record my whole screen")*
• "Check the recording status now."
• "Show me the live transcript so far."
• "Pause the recording." · "Resume it."
• "Take a screenshot."
• "Stop the recording."
• "List my recordings again — the new one should be on top."
• "Give me the summary and transcript of that recording."
• "Regenerate its summary using one of my templates."
• "Search my recordings for the word ''."
• "Rename that recording to 'MCP dual-mode test'."
• "Get the full asset bundle for it."
• "Save this text as a note/artifact on that recording: ."

Cloud mode — your synced library (no app needed)

• "List my 5 most recent SeaMeet recordings." · "What did I record in the last 7 days?"
• "Give me the summary of the top recording."
• "Now show its action items and key decisions."
• "Pull the full speaker-labeled transcript for it, and its chapters."
• "Get me a download/stream link for that recording's media."
• "How much SeaMeet storage am I using versus my quota?"
• "Create a webhook to `https://webhook.site/` that fires when AI results are ready."
• "List my webhooks with their delivery health and signing secret."
• "Update that webhook to also fire on `recording.synced`."
• "Delete that webhook."
• "What's my SeaMeet connection status?"
• "Disconnect my SeaMeet cloud account." *(forgets the cached key; the next cloud call re-authorizes)*

How it works

A thin stdio↔HTTP proxy. The SeaMeet desktop app hosts a localhost-only bridge (`127.0.0.1:3741`, fallbacks 3742/3743) authenticated with a per-launch random secret; on startup it writes credentials to `$TMPDIR/seameet-mcp-bridge-.json` (mode 0600), which this server reads and proxies (`tools/list` → `GET /mcp-bridge/tools`, `tools/call` → `POST /mcp-bridge/call-tool`). Nothing leaves your machine in desktop mode. Cloud mode talks to the hosted SeaMeet worker over HTTPS with your minted key.

Full tool reference (for LLMs): seameet.ai/llms.txt — also served locally at `http://localhost:3741/llms.txt` while the app runs.

Errors are machine-readable

Tool failures return structured JSON your agent can branch on:

{ "success": false, "error": { "code": "app_not_running", "tool": "seameet_start_recording",
  "message": "The SeaMeet desktop app is not running.",
  "install": { "macos": "brew install --cask seameet-ai/tap/seameet", "windows": "winget install seameet" },
  "hint": "Ask the user to install and launch it, then retry." } }

Configuration (rarely needed)

Development

npm install
npm test             # credentials discovery + end-to-end stdio client against a fake bridge + fake cloud
npm run build:mcpb   # validate manifest.json + pack the Claude Desktop extension

Releasing is automated — see PUBLISHING.md.

Legal

• Terms: https://seameet.ai/en/terms/
• Privacy: https://seameet.ai/en/privacy/

License

MIT © SeaMeet.ai