ClipDock

A micro MCP App for ChatGPT: capture and review snippets, links, results and fragments tied to a conversation, in a native surface BESIDE the chat (an official OpenAI MCP Extensions entrypoint — thread panel), never inside the message flow.

Surfaces

• Thread entrypoint — opens a ClipDock panel beside the current conversation (desktop).
• Inline fallback — clipdock_panel can also render inline when the host does not expose the entrypoint.

Honesty

• The MCP endpoint is PUBLIC (no login, no OAuth). Isolation is PER-WORKSPACE by a SECRET KEY (capability). DURABLE storage is used ONLY for a PROTECTED (key-owned) workspace — its clips are bound to the key holder and cannot be read without the key. An UNPROTECTED namespace (e.g. 'default') has no owner, so its clips are EPHEMERAL: NEVER written to durable storage, lost on cold start. Create a protected workspace (workspace_create / workspace_protect) to store durable, private clips; the key is shown once and stored only as a SHA-256 hash.
• Because the host passes no reliable user identity to a no-auth endpoint, the owner binding is the secret key; the server never stores content durably without that binding. Account-level authentication would be added before any shared or sensitive deployment.
• Writes require confirm:true. Clips are archived (status flip), never hard-deleted. The activity log is append-only.
• Every control in the panel maps to a real clip tool, or is hidden / disabled with a reason — no decorative buttons.
• The panel never imitates ChatGPT's native history, Projects or account settings.

MCP endpoint: /api/mcp (also /mcp) · stateless · no authentication.

Privacy · Terms · Panel preview · Support: infodev@mmcco.co