SeaMeet MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEAMEET_API_KEY | No | Cloud API key (smk_…) — skips the device authorization flow | |
| SEAMEET_DEVICE_URL | No | Override the device authorization endpoint (default: production) | |
| SEAMEET_REMOTE_URL | No | Override the cloud endpoints (default: production) | |
| SEAMEET_BRIDGE_PORT | No | Port for the desktop bridge (used with SEAMEET_BRIDGE_SECRET to bypass credentials file) | |
| SEAMEET_BRIDGE_SECRET | No | Secret for the desktop bridge (used with SEAMEET_BRIDGE_PORT to bypass credentials file) | |
| SEAMEET_MCP_CREDENTIALS_FILE | No | Explicit path to the desktop-bridge credentials file | |
| SEAMEET_CLOUD_CREDENTIALS_FILE | No | Where the minted cloud key is cached (default ~/.seameet/credentials.json) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| seameet_list_recent_recordingsA | List 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_recordingA | Get one recording's metadata plus a chosen artifact. sections: "summary" (Markdown), "transcription" (speaker-labeled), "chapters", "action-items", "key-decisions", or "all" for every section. Content may be capped for free-plan owners (capped=true). |
| seameet_get_media_urlA | Get a fresh presigned URL (15 min) to stream/download a recording's media file. |
| seameet_get_usageA | Storage usage vs quota for the authenticated account. |
| seameet_create_webhookA | Register an outbound webhook endpoint. SeaMeet POSTs signed event deliveries to |
| seameet_list_webhooksA | List 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_webhookA | Update 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_webhookA | Delete a webhook endpoint by id. Requires a write-scoped key. |
| seameet_statusA | Report 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. |
| seameet_logoutA | Disconnect CLOUD mode: forget the cached cloud API key (~/.seameet/credentials.json) and cancel any pending device authorization, so the next cloud tool call re-authorizes (e.g. to switch accounts). Does not touch DESKTOP mode. The key itself stays valid until you revoke it under API keys at https://app.seameet.ai/account. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose (webhook CRUD, recording retrieval, media URL, usage, status, logout), with no overlapping functionality. Descriptions further clarify boundaries.
All tools follow the 'seameet_verb_noun' pattern (e.g., seameet_create_webhook, seameet_get_recording), with only minor deviations (seameet_logout, seameet_status) that are still intuitive and consistent with the prefix.
10 tools cover webhook management, recording access, usage, and session controls—well-scoped for a meeting recording MCP server. Neither too sparse nor overwhelming.
Covers core workflows: webhook lifecycle, recording retrieval, media URL, usage, and authentication state. Minor gaps (e.g., no recording deletion or search) but overall sufficient for the stated purpose.