ClipDock is a stateless MCP connector. It processes only the content you pass to its tools in order to compute a response for that same request.
Write tools (clip_add, clip_update, clip_archive) store clips under a namespace you choose (workspace_id). Storage is owner-gated: clips in a protected workspace (one with a secret key) are kept in a durable private store (Vercel Blob, private at rest) and are bound to the key holder; clips in an unprotected namespace are ephemeral — they are never written to durable storage and are lost on cold start. Read tools return those clips.
The MCP endpoint is public (no login, no OAuth). Access control is per-workspace by a secret key (a capability token): an unprotected workspace_id is a namespace, not an access boundary. Protect a workspace with workspace_create or workspace_protect; afterwards every read and write requires that secret key. The key is shown once, stored only as a SHA-256 hash, and never recoverable. Real multi-user authentication is the pre-publish gate; this pilot is private/draft.
No accounts, no tracking, no advertising, no sale of data, no calls to third-party services.
Clips are archived (kept with status=archived), never hard-deleted, so an original is always recoverable. To have stored clips removed, contact support.
Support: infodev@mmcco.co