SeaMeet MCP

by seameet-ai

Not rated
GitHub

About

Connect AI agents to SeaMeet meeting recordings, transcripts, summaries, screenshots, and recording controls.

Details

Author
seameet-ai
Categories
Productivity

Setup

Install SeaMeet MCP in your MCP client (Claude Desktop, Cursor, Windsurf, and others).

Repository: https://github.com/seameet-ai/seameet-mcp

Follow the installation instructions in the repository README, then restart your MCP client.

TheSeaMeetMCP server — let AI agentsrecord, 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 isrunning, 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 yoursynced 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/listreturns the superset of whatever's available; callseameet_statusany time to see the current mode(s).

- 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 thelive transcriptmid-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 generatedartifacts(summary, transcript, SRT, chapters, action items, key decisions, screenshot OCR/description) —seameet_get_artifact
- Searchacross 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 summaryfrom a template —seameet_regenerate_summary· list templates —seameet_list_templates

- List recent synced recordings —seameet_list_recent_recordings· fetch summary / transcript / chapters / action items / key decisions —seameet_get_recording
- Get a temporary mediastream/download URLseameet_get_media_url
- Check storage usage —seameet_get_usage
- Manage outboundwebhooks(signed deliveries onai.ready/recording.synced) —seameet_create_webhook·seameet_list_webhooks·seameet_update_webhook·seameet_delete_webhook

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

That's17 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.

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

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

Install the SeaMeet MCP server — fetchhttps://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.

The generic block, accepted by most MCP clients:

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

- Node.js ≥ 18.
- For desktop mode: theSeaMeet desktop appinstalled andrunningbrew install --cask seameet-ai/tap/seameet(macOS) orwinget install seameet(Windows). Needsv3.2.0+; an older running app reportsapp_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 provideSEAMEET_API_KEYor 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), clickAuthorize, and a read+write key is minted and cached at~/.seameet/credentials.json. Silent thereafter; revoke any time underAPI keyson your account. To disconnect or switch accounts, callseameet_logout(orrm ~/.seameet/credentials.json).

manifest.jsonis anMCPBbundle manifest, so the server ships as a one-click Claude Desktop extension:

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

Install viaSettings → Extensions → Advanced → Install extension…and pickdist/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/seameetskill)

This repo doubles as aClaude Code plugin marketplace. The plugin registers the MCP serveranda/seameetskill 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

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.

- "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: <!-- -->."

- "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 tohttps://webhook.site/<your-id>that fires when AI results are ready."
- "List my webhooks with their delivery health and signing secret."
- "Update that webhook to also fire onrecording.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)

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-<username>.json(mode 0600), which this server reads and proxies (tools/listGET /mcp-bridge/tools,tools/callPOST /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 athttp://localhost:3741/llms.txtwhile the app runs.

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." } }
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 — seePUBLISHING.md.

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

The 1Password MCP server creates a bridge that allows MCP clients such as Codex and Kiro to manage your 1Password Environments with secure authorization prompts.

This is the 1st, easiest, and cheapest PPT, slides, presentation AI generation MCP Server in the world.

Persistent memory for any AI assistant. Zero token cost until recall. Stores memories in local SQLite, ranks by 6-factor scoring, returns results 79% smaller than JSON. Works with Claude, ChatGPT, Grok, Cursor, Windsurf, and any MCP client.

A MCP server that enables AI assistants to interact with Anki, the spaced repetition flashcard application.

Enables LLM clients to interact with macOS applications through AppleScript. Built using the @beyondbetter/bb-mcp-server library, this server provides safe, controlled execution of predefined scripts with optional support for arbitrary script execution.

An MCP server for WordPress plugin audits

Turn your AI assistant into a digital marketing hub that creates, organizes, and analyzes links and QR Codes on demand.

Connect AI clients to Cal.com scheduling through the Model Context Protocol using the hosted server at mcp.cal.com or a local instance.

Sync Calendars, Scheduling Links, AI Executive Scheduling Assistant, Unified Calendar

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.