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.
No install and no API key: paste this URL as a custom connector in claude.ai, ChatGPT, or their desktop apps, then sign in with your SeaMeet account and click Allow. Works on every plan, free included.
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.
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), rename speakers, re-summarize recordings, transcribe files from your computer, 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 |
seameet_rename_speakers | Cloud: replace “Speaker 1”, “Speaker 2” with real names in a synced recording’s transcript and summary |
seameet_regenerate_recording_summary | Cloud: re-summarize a synced recording, optionally with a different template |
seameet_transcribe_file | Upload an audio or video file from your computer and get it transcribed and summarized in your library |
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.1only — 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
Can I use SeaMeet inside Claude or ChatGPT without installing anything?
Yes. Add https://mcp.seameet.ai/mcp as a custom connector in claude.ai, the Claude desktop app, ChatGPT, or the ChatGPT desktop app, then sign in with your SeaMeet account and click Allow. No install and no API key. Any SeaMeet account works, including the free plan; Sync Pro unlocks full search snippets and full Meeting Memory pages.
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.
Links
- Claude & ChatGPT connector guide: Use SeaMeet in Claude and ChatGPT
- npm package: @seameet/mcp
- Source: github.com/seameet-ai/seameet-mcp
- MCP feature overview: desktop-app/features/mcp-server
- Web app API (Sync Pro, OpenAPI 3.1): app.seameet.ai/api
- Site map for LLMs: seameet.ai/llms.txt