Model Context Protocol

How ChatGPT and Claude open the editor.

Ask your assistant to find a moment. BitterClip pulls up the transcript, opens the editor in the conversation, renders the MP4, and keeps the timing tied to the audio.

The assistant picks words. BitterClip handles the cut, captions, export, and final approval without guessed timestamps.

Start with one recording

Live · running below

This is the editor ChatGPT and Claude open.

The transcript editor below is the exact BitterClip editor that opens inside ChatGPT and Claude. It is mounted here so you can try the same review surface: drag across the words to cut a clip; press play and watch the cursor land on the word.

One editor. Wherever you are already working.

Live editor · demo mode try it
Loading the editor…

Fixtures only — every edit is stubbed, no backend, no account, no render cost. Point the same component at a live backend and it does the real work.

ChatGPT App Directory

Submit it as BitterClip.

The public app should be named BitterClip and submitted from a verified BitterClip or Bitter Platform organization. Its job is narrow: find source-linked clip candidates from a user's recordings, open the transcript editor, create approved clips, export MP4s, and prepare publishing packages only when the user asks.

Public fields

  • App name: BitterClip
  • Website: https://bitterclip.com
  • Privacy: https://bitterclip.com/privacy
  • Terms: https://bitterclip.com/terms
  • Support: hello@bitterclip.com
  • MCP resource: https://app.bitterclip.com/mcp

Review flow

  • Test the remote MCP server in ChatGPT Developer Mode before submission.
  • Scan the live MCP endpoint in the OpenAI Platform Dashboard after the backend deploy that defines the final tool list.
  • Provide screenshots, test prompts, expected responses, and a demo account with sample recordings in the dashboard.

Submission boundaries

  • Do not publish OAuth secrets, demo credentials, provider payloads, or private review accounts in this repository.
  • Keep billing checkout on BitterClip's own domain; the submitted ChatGPT toolset should not expose checkout or subscription purchase tools.
  • Publishing tools should be labeled as write and open-world actions, and should run only after explicit user approval.

The MCP Endpoint (POST /mcp)

The BitterClip backend speaks JSON-RPC 2.0 over HTTP — CORS, origin checks, and bearer-token auth. Tool calls route to your workspace.

Protocol Version

MCP over JSON-RPC 2.0, plus the MCP Apps UI extension (stable spec 2026-01-26) that mounts interactive widgets inside the chat.

Supported Methods

  • initialize — Handshake and exchange capabilities
  • ping — Connection heartbeat verification
  • tools/list — Expose available editor capabilities
  • tools/call — run a tool — find moments, create or export a clip
  • resources/list — Ingested audio/video resources
  • resources/read — read a recording's transcript and clips
JSON-RPC Requesttools/list
{
  "jsonrpc": "2.0",
  "method": "tools/list",
  "params": {},
  "id": 1
}