Use SeaMeet with AI agents

SeaMeet ships an MCP server so AI agents — Claude Code, Codex, Cursor, Claude Desktop, Windsurf — can operate the recorder on your machine: start and stop recordings, take screenshots, read the live transcript mid-meeting, and search every summary and action item in your library. Works with or without the desktop app; no bot ever joins your calls.

Already inside a coding agent? Paste this — it fetches the guide and installs itself:

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 install it yourself

npx -y @seameet/mcp

Runs in any MCP client. Prefer your tool's own shortcut:

Claude Code claude mcp add seameet -- npx -y @seameet/mcp

Codex codex mcp add seameet -- npx -y @seameet/mcp

Copilot CLI copilot mcp add seameet -- npx -y @seameet/mcp

Cursor Add to Cursor (one-click)

Setup

Or add it yourself (one line)

No desktop app required to start; see the two modes below.

Claude Code

claude mcp add seameet -- npx -y @seameet/mcp

Codex CLI — add to ~/.codex/config.toml

[mcp_servers.seameet]
command = "npx"
args = ["-y", "@seameet/mcp"]

Cursor / Claude Desktop / Windsurf — JSON config

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

That's it. The tool list is fetched live, so new SeaMeet releases add capabilities to your agent automatically.

Two modes: desktop & cloud

One install adapts to what's available — @seameet/mcp picks the richer backend automatically and exposes the union of both. Call seameet_status any time to see the current mode(s).

Desktop mode — when the SeaMeet desktop app (Windows/macOS) is installed and running, agents get the full recorder toolset: start/stop/pause recordings, screenshots, live transcript, and read/search/save artifacts. Nothing leaves your machine. (download)
Cloud mode — with no desktop app, agents read your synced library (recordings, transcripts, summaries) and manage webhooks over the network. The first cloud call shows a short code + a link; you approve it once in the web app (no key copy/paste) and a scoped key is minted and cached — silent thereafter. Cloud access requires SeaMeet Sync Pro.

Try it

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

What agents can do

Tool	What it does
`seameet_start_recording`	Start recording: microphone, screen, or screen + system audio
`seameet_stop_recording`	Stop and save the current recording
`seameet_pause_recording / seameet_resume_recording`	Pause and resume audio recordings
`seameet_recording_status`	Check whether a recording is active
`seameet_take_screenshot`	Capture a screenshot
`seameet_get_live_transcript`	Read the live transcript mid-meeting
`seameet_list_recordings`	List recordings and screenshots with metadata
`seameet_get_artifact`	Read summaries, transcripts, action items, key decisions, chapters, OCR
`seameet_search_text`	Search across every recording’s text content
`seameet_save_artifact`	Save agent-generated content back to a recording
`seameet_regenerate_summary`	Re-summarize a recording with a chosen template

Full machine-readable reference: seameet.ai/llms.txt

Killer workflows

Capture a bug report

"I can’t reproduce this — record my screen while I show you, then debug from the transcript and screenshots."

Meeting → code

"Read the action items from this morning’s standup recording and turn them into GitHub issues."

Instant demo video

"Record my screen for 2 minutes while I walk through the new feature, then draft the release notes from the transcript."

Org memory

"Search my recordings — what did we decide about pricing in April?"

How it works & security

The desktop app hosts a local HTTP bridge on 127.0.0.1 only — nothing is exposed to the network.
Every request is authenticated with a per-launch random secret (written to a file only your OS user can read).
File access is confined to the SeaMeet save directory.
Errors are structured JSON with machine-readable codes (app_not_running, timeout, …) so agents recover gracefully.

FAQ

Do I need the SeaMeet desktop app to use the MCP server?

No. Cloud mode reads your synced library (recordings, transcripts, summaries) without the app. Desktop mode adds the full recorder toolset — start/stop recordings, screenshots, live transcript — when the desktop app is installed and running.

Do I need to copy and paste an API key?

No. Desktop mode needs no auth at all. Cloud mode uses a one-time device authorization: the agent shows a short code and a link, you approve it once in the web app, and a scoped key is minted and cached automatically.

Which AI agents and tools are supported?

Any MCP client: Claude Code, Codex, Cursor, Claude Desktop, Windsurf, GitHub Copilot CLI, and others. Every one runs the same command, npx -y @seameet/mcp.

Is my meeting data sent anywhere?

In desktop mode nothing leaves your machine — the server talks to a localhost-only bridge. Cloud mode only accesses recordings you have explicitly synced.