Integration · Claude Code (Anthropic)

Claude Code ⇄ SwiftyClip

SwiftyClip is MCP-native. Claude Code finds our ten clip.* tools automatically, so you can drive the whole clipping pipeline from a single prompt without opening the Mac app.

1. Install SwiftyClip

Grab the notarized DMG from /download and drag it to Applications. Launch it once; a loopback TCP bridge starts automatically for the MCP layer to reach.

2. Register the MCP server

Add this to your Claude Code config (Desktop: Settings → MCP servers, or edit ~/.config/claude-code/mcp-servers.json):

{
  "mcpServers": {
    "swiftyclip": {
      "command": "swiftyclip",
      "args": ["mcp"]
    }
  }
}

Prefer WebSocket? SwiftyClip v1.0.4 also supports a loopback WebSocket transport on ws://127.0.0.1:8765:

$ swiftyclip mcp --transport websocket --port 8765

3. Prompt Claude

Now you can just talk to Claude Code. A good starter prompt:

Use swiftyclip_mcp to process ~/Movies/episode.mp4. Score all segments, render the top 3 with bold captions to ~/Desktop/NewClips/, and list the resulting file paths.

Claude chains clip.ingest → clip.analyze → clip.scoreSegments → clip.render three times. You don't open the Mac app — you just get the files.

Common prompts

Rerank by topic — "Find clips about building an AI startup from project X, render the best 2."
Schedule a week — "Render 7 clips from project Y and schedule them daily at 9am ET."
Transcribe only — "Import ~/Audio/talk.mp3 and give me the full transcript."
Dedupe pass — "Keep the 5 scored segments with the least topical overlap and render them."

Full transcripts for each pattern are on /agents/examples.

Security

SwiftyClip's MCP server binds to loopback only. Video and audio never leave your Mac. The only outbound network calls are to Supabase (scheduling metadata) and Stripe (billing). Full detail: /security-whitepaper.