Seameet MCP vs Google Workspace MCP

A side-by-side look at the Seameet MCP and Google Workspace MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Seameet MCP logoSeameet MCPWorkplace & Productivity · Local subprocess (stdio)Connect AI agents to SeaMeet meeting recordings, transcripts, AI summaries, screenshots, action items, webhooks, and desktop recorder controls.63GoodAuth: not declaredGoogle Workspace MCP logoGoogle Workspace MCPWorkplace & Productivity · Local subprocess (stdio)Comprehensive Google Workspace MCP server with full support for Google Calendar, Drive, Gmail, and Docs, Forms, Chats, Slides and Sheets over stdio, Streamable HTTP and SSE transports.68GreatAuth: oauth 2.0

Verdict: choose Seameet MCP for workplace & productivity work as a local process; choose Google Workspace MCP for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Seameet MCP logoChoose Seameet MCP when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: SEAMEET_API_KEY.
  • You want tools like seameet_desktop_recording_help, seameet_list_recent_recordings, seameet_get_recording.
Explore Seameet MCP

Google Workspace MCP logoChoose Google Workspace MCP when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
  • You want tools like start_google_auth, search_gmail_messages, get_gmail_message_content.
Explore Google Workspace MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSeameet MCP logoSeameet MCPGoogle Workspace MCP logoGoogle Workspace MCP
CategoryWorkplace & ProductivityWorkplace & Productivity
Quality signal63/100 · Good68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredOAuth 2.0
PricingNot declaredFree
Required env varsSEAMEET_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars13,400
Directory activity 2 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools14123

Tools & capabilities

Seameet MCP tools 14

  • seameet_desktop_recording_helpExplain how to enable local SeaMeet desktop recording tools. Use this when the user asks to record a meeting, call, webinar, interview, screen, microphone, system audio, live transcript, or screenshot but this cloud MCP server does not expose local recorder controls. Cloud MCP can read synced recordings and manage webhooks; starting/stopping local recordings requires the SeaMeet desktop app plus the local @seameet/mcp server. Provides the fast install commands: macOS `brew install --cask seameet-ai/tap/seameet`, Windows `winget install seameet`.
  • seameet_list_recent_recordingsList recordings in the SeaMeet cloud library, newest first. Returns compact entries {assetId, title, kind, durationMs, updatedAt, shared}. Use seameet_get_recording to fetch one recording's transcript/summary/action items.
  • seameet_get_recordingGet one recording's metadata plus a chosen artifact. section: "summary" (Markdown), "transcription" (one "[hh:mm:ss] Speaker: text" line per segment), "chapters" (JSON), "action-items" and "key-decisions" (JSON; desktop recordings only — files transcribed on app.seameet.ai have summary, transcription and chapters), or "all". A long summary or transcription is paged: pass pagination.nextOffset back as offset to continue; if pagination.sectionVersion changes between pages the text was edited, so start over at offset 0. JSON sections are returned whole. asset.transcriptionJob reports a file transcription that is still running or failed. Content may be capped for free-plan owners (capped=true).
  • seameet_get_media_urlGet a fresh presigned URL (15 min) to stream/download a recording's media file.
  • seameet_get_usageStorage usage vs quota for the authenticated account.
  • seameet_rename_speakersRename speakers in one of your recordings: the transcript, summary, chapters, action items and key decisions all update. Pass labels exactly as seameet_get_recording lists them in `speakers` (e.g. "Speaker 1"), and the transcription's pagination.sectionVersion as transcriptVersion so a transcript that changed since you read it is refused ("stale") instead of renaming the wrong voice. Owner only; needs a WRITE-scoped key. On error "conflict", call again with the same renameId, the same transcriptVersion, and skip set to the returned `landed`.
  • seameet_regenerate_recording_summaryRegenerate the AI summary and chapters of one of your recordings from its current transcript (Meeting Minutes format). Returns immediately; the new summary lands in about 1-2 minutes: poll seameet_get_recording(assetId, section:"summary") until pagination.sectionVersion is greater than previousSummaryVersion (asset.summaryRun.state "failed" means it failed). Owner only; needs a WRITE-scoped key. At most once per recording per 5 minutes and 20 per day. Screenshots in the recording's notes are not analyzed.
  • seameet_create_webhookRegister an outbound webhook endpoint. SeaMeet POSTs signed event deliveries to `url` (a PUBLIC https server the user hosts — MCP cannot receive them). Events: "recording.synced" (a recording finished syncing) and "ai.ready" (the summary and every other AI artifact inlined). ai.ready fires each time the summary is written — again when it is regenerated or speakers are renamed — so one recording can deliver it more than once, possibly out of order; per assetId keep the delivery with the greatest data.artifactsRevision. Requires a WRITE-scoped key + Sync Pro; the returned `secret` signs deliveries (HMAC-SHA256). Full contract: https://app.seameet.ai/api/
  • seameet_list_webhooksList the account's webhook endpoints with signing secrets and delivery health (failure_count, last_status, active). Use the ids with seameet_update_webhook / seameet_delete_webhook.
  • seameet_update_webhookUpdate an endpoint: re-enable one auto-disabled by failures (active:true, which also resets the failure counter) and/or change its url/events. Requires a write-scoped key.
  • seameet_delete_webhookDelete a webhook endpoint by id. Requires a write-scoped key.
  • seameet_statusReport how this SeaMeet MCP is connected: DESKTOP mode (the desktop app is running — full record/screenshot/transcript tools) and/or CLOUD mode (authorized access to your synced library + webhooks). Call this to see the current mode and how to enable the other.
  • +2 more on the listing page

Google Workspace MCP tools 123

  • start_google_authManually initiate Google OAuth authentication flow. NOTE: This is a legacy OAuth 2.0 tool and is disabled when OAuth 2.1 is enabled. The authentication system automatically handles credential checks and prompts for authentication when needed. Only use this tool if: 1. You need to re-authenticate with different credentials 2. You want to proactively authenticate before using other tools 3. The automatic authentication flow failed and you need to retry In most cases, simply try calling the Google Workspace tool you need - it will automatically handle authentication if required.
  • search_gmail_messagesSearches messages in a user's Gmail account based on a query. Returns both Message IDs and Thread IDs for each found message, along with Gmail web interface links for manual verification. Supports pagination via page_token parameter.
  • get_gmail_message_contentRetrieves the full content (subject, sender, recipients, body) of a specific Gmail message. Bodies are returned inline and truncated at 20,000 characters. Set full=True to get the complete, untruncated message instead: it is exported to disk and the response carries a short-lived download URL (HTTP transport) or file path (stdio transport) rather than the body, so large messages never stream through the model context. Stateless deployments have no file storage, so there full=True returns the untruncated body inline.
  • get_gmail_messages_content_batchRetrieves the content of multiple Gmail messages in a single batch request. Supports up to 25 messages per batch to prevent SSL connection exhaustion.
  • get_gmail_attachment_contentDownloads an email attachment and saves it to local disk. In stdio mode, returns the local file path for direct access. In HTTP mode, returns a temporary download URL (valid for 1 hour). May re-fetch message metadata to resolve filename and MIME type.
  • send_gmail_messageSends an email using the user's Gmail account. Supports new emails, replies, and forwards, with optional attachments. Supports Gmail's "Send As" feature to send from configured alias addresses. To forward an existing message, pass forward_message_id. The original subject, body (quoted with a "Forwarded message" header), and attachments are carried over. In forward mode, body (if any) is prepended as a note and subject is optional. Threading, reply, and signature options do not apply when forwarding. THIS TOOL SENDS IMMEDIATELY AND CANNOT SCHEDULE. Gmail's REST API exposes no send-time parameter; Schedule send is a web-UI feature with no API equivalent, so no argument to this tool can defer delivery. Never tell a user a message was scheduled. For "prepare now, deliver later", create a draft with draft_gmail_message. An external scheduler must retain the message data to create and send a new message via send_gmail_message at the chosen time, or call users.drafts.send with the draft ID returned by draft_gmail_message. Alternatively, let the user schedule that draft in the Gmail UI.
  • draft_gmail_messageCreates a draft email in the user's Gmail account. Supports both new drafts and reply drafts with optional attachments. Supports Gmail's "Send As" feature to draft from configured alias addresses. SCHEDULED SEND IS NOT AVAILABLE. Gmail's REST API exposes no send-time parameter; the Schedule send feature is web-UI only, and a message cannot be placed in the Scheduled folder through the API. Do not claim a message was scheduled. To deliver at a chosen time, create a draft with draft_gmail_message. An external scheduler must retain the message data to create and send a new message via send_gmail_message then, or call users.drafts.send with the draft ID returned by draft_gmail_message. Alternatively, let the user schedule the draft in the Gmail UI.
  • get_gmail_thread_contentRetrieves the complete content of a Gmail conversation thread, including all messages. Optionally also returns structured ownership analysis so a caller can determine who sent the last message and who owes whom a response without re-parsing the formatted string or making a second tool call.
  • get_gmail_threads_content_batchRetrieves the content of multiple Gmail threads in a single batch request. Supports up to 25 threads per batch to prevent SSL connection exhaustion.
  • list_gmail_labelsLists labels in the user's Gmail account.
  • manage_gmail_labelManages Gmail labels: create, update, or delete labels.
  • list_gmail_filtersLists all Gmail filters configured in the user's mailbox.
  • +111 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Seameet MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "seameet-ai-seameet-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@seameet/mcp"
      ],
      "env": {
        "SEAMEET_API_KEY": "YOUR_SEAMEET_API_KEY_HERE"
      }
    }
  }
}

Google Workspace MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "taylorwilsdon-google-workspace-mcp": {
      "command": "uvx",
      "args": [
        "workspace-mcp"
      ]
    }
  }
}

Frequently asked questions

Seameet MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. Google Workspace MCP belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Seameet MCP for workplace & productivity work and Google Workspace MCP for workplace & productivity.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Seameet MCP has no declared pricing — check the project's own site. Google Workspace MCP is listed as free. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add seameet-ai-seameet-mcp and taylorwilsdon-google-workspace-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Seameet MCP has a quality signal of 63/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Google Workspace MCP has 68/100 (Great) with 4 views, 0 installs and 3,400 GitHub stars.