Seameet MCP vs Clickup
A side-by-side look at the Seameet MCP and Clickup MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Seameet MCP for workplace & productivity work as a local process; choose Clickup 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?
Choose 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.
Choose Clickup when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 63/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | SEAMEET_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 52 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 14 | Not listed |
| Full listing | View Seameet MCP | View Clickup |
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
Clickup tools
No tool names declared yet. Check the project README from 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": {
"seameet-ai-seameet-mcp": {
"command": "npx",
"args": [
"-y",
"@seameet/mcp"
],
"env": {
"SEAMEET_API_KEY": "YOUR_SEAMEET_API_KEY_HERE"
}
}
}
}
Clickup
{
"mcpServers": {
"clickup-2": {
"command": "npx",
"args": [
"-y",
"@taazkareem/clickup-mcp-server@latest"
]
}
}
}
Frequently asked questions
Seameet MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. Clickup belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Seameet MCP for workplace & productivity work and Clickup 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. Clickup has no declared pricing — check the project's own site. 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 clickup-2 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. Clickup has 49/100 (Fair) with 2 views, 0 installs and 52 GitHub stars.