Seameet MCP vs Dreamwork

A side-by-side look at the Seameet MCP and Dreamwork 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 declaredDreamwork logoDreamworkWorkplace & Productivity · Remote HTTP/SSEJob search, application materials, and application tracking for AI assistants.75GreatAuth: api key required

Verdict: choose Seameet MCP for workplace & productivity work as a local process; choose Dreamwork for workplace & productivity over a hosted endpoint. 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

Dreamwork logoChoose Dreamwork when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: DREAMWORK_API_KEY, DREAMWORK_API_URL, DREAMWORK_UNREAD_NOTICES, DREAMWORK_TELEMETRY, DO_NOT_TRACK.
  • You want tools like list_matches, get_job, save_job.
Explore Dreamwork

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSeameet MCP logoSeameet MCPDreamwork logoDreamwork
CategoryWorkplace & ProductivityWorkplace & Productivity
Quality signal63/100 · Good75/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredAPI key required
PricingNot declaredNot declared
Required env varsSEAMEET_API_KEYDREAMWORK_API_KEYDREAMWORK_API_URLDREAMWORK_UNREAD_NOTICESDREAMWORK_TELEMETRYDO_NOT_TRACK
Verified ownerCommunity listingCommunity listing
GitHub stars112
Directory activity 2 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools1471

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

Dreamwork tools 71

  • list_matchesReturns the account's ranked live match pool with job id, its Dreamwork page url, title, company, location, remote terms, salary, dates, match percent and saved/applied state. Filters narrow that pool; nextCursor continues a page with identical filters, and null ends the walk. A page holds 10 jobs by default and limit accepts up to 50; the next page is the previous nextCursor, which keeps the page size it was issued with. addedAfter supports overlapping discovery windows because listings can become servable after first discovery. notes describe applied filters and coverage.
  • get_jobReturns one saved or corpus role by id with full description, company, location and remote terms, salary, posted date, match score, saved state, board column, application id, material readiness and work-eligibility verdict. url is the Dreamwork listing page; sourceUrl is the employer's direct posting. eligible is true for an unrestricted role or a confirmed allowed country, false for a high-confidence restriction excluding confirmed countries, and null when eligibility is unknown. Only false blocks applying or Autopilot: null means eligibility is not yet known, so proceed with applying — the application itself surfaces any real restriction. whyItMatches may be empty when no matcher explanation is stored.
  • save_jobSaves one role to the account's pipeline at SAVED as a bookmark. No application is submitted or queued until apply is called. Application materials may start preparing in the background. An already saved role returns a no-op receipt.
  • dismiss_matchHides one role, every listing with the same employer and title in any location, from the account's match feed, job alerts and Autopilot until the account restores or saves it. The receipt offers undo for one minute; restore_match reverses it at any time and list_dismissed_matches lists dismissed listings. The supplied reason is not stored. It does not hide other roles from the same company and does not move or remove an existing pipeline card.
  • restore_matchReverses the dismissal of a role, every listing with the same employer and title, so it can return to the account's match feed, job alerts and Autopilot. Restoring a listing that is not dismissed returns a no-op receipt. Restoring does not save the listing. A closed listing stays out of the feed.
  • list_dismissed_matchesReturns the account's dismissed listings, newest first, with listing id, title, company, Dreamwork page url, dismissal time and whether the listing is still active. total counts all dismissed listings. limit defaults to 20 and accepts up to 50; nextOffset continues the list and null ends it.
  • get_pipelineReturns saved and applied roles as board cards with column, application id and last-updated time. total and counts cover all matching records; complete identifies whether cards are truncated by limit. limit defaults to 50 cards and accepts up to 100; there is no next page, so when complete is false narrow the read with status. Column values describe board state and do not establish employer receipt or response.
  • move_pipelineMoves one role's board card to the requested column using the account holder's reported state. No employer is contacted. APPLIED records an application rather than submitting one; INTERVIEWING creates a durable interview record. WITHDRAWN removes the card from the active board. Closing a role can remove its listing from the feed. A receipt offers undo only when reversible.
  • mark_applied_offsiteRecords an application the account holder submitted outside Dreamwork. Exactly one of matchId, listingId or url names the role; a role not yet in the pipeline is added in Applied without generating materials, and an unlisted URL is imported in the background. appliedAt (YYYY-MM-DD or ISO 8601, not in the future) is the reported application date and defaults to now; repeating the call with a new appliedAt corrects it. attestation:true is required and represents the person's confirmation that submission occurred. Recorded roles are excluded from matches and Autopilot. Applications Dreamwork is still sending are refused. There is no undo. This call does not send an application.
  • import_jobFetches a public job-posting URL and imports it as a private role in the account's pipeline. Extraction runs asynchronously and the card appears when it finishes. A posting already held by Dreamwork returns completed without another fetch.
  • cancel_applyStops a queued or in-progress application when submission can still be prevented. Already submitted applications cannot be recalled; the receipt reports that boundary.
  • generate_packQueues a tailored resume, cover letter and employer-question answers for one saved role. assets optionally selects a subset; omission requests all three. Each request spends one pack allowance, regardless of subset, and generation settles asynchronously. Existing materials can be overwritten by generation.
  • +59 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"
      }
    }
  }
}

Dreamwork

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dreamwork-2": {
      "command": "npx",
      "args": [
        "-y",
        "@dreamworkhq/mcp"
      ],
      "env": {
        "DREAMWORK_API_KEY": "YOUR_DREAMWORK_API_KEY_HERE",
        "DREAMWORK_API_URL": "YOUR_DREAMWORK_API_URL_HERE",
        "DREAMWORK_UNREAD_NOTICES": "YOUR_DREAMWORK_UNREAD_NOTICES_HERE",
        "DREAMWORK_TELEMETRY": "YOUR_DREAMWORK_TELEMETRY_HERE",
        "DO_NOT_TRACK": "YOUR_DO_NOT_TRACK_HERE"
      }
    }
  }
}

Frequently asked questions

Seameet MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. Dreamwork belongs to Workplace & Productivity and uses a remote HTTP/SSE transport. Pick Seameet MCP for workplace & productivity work and Dreamwork 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. Dreamwork has no declared pricing — check the project's own site. Auth: api key required. 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 dreamwork-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. Dreamwork has 75/100 (Great) with 2 views, 0 installs and 12 GitHub stars.