MCP server

Cliphi hosts a remote MCP server that exposes the Agent API as tools:

https://www.cliphi.com/api/mcp

• Transport: Streamable HTTP, stateless, JSON responses. POST your JSON-RPC messages; there is no server-initiated SSE stream (GET returns 405). Both /api/mcp and /api/mcp/ work.
• Auth, two doors: chat clients (Claude, Grok, Le Chat, Perplexity) connect via OAuth 2.1: add the URL, the client opens a Cliphi sign-in page, you approve once. CLIs, configs, and scripts can instead send an API key as Authorization: Bearer chp_live_.... Same guards, same billing as REST either way. Discovery, dynamic client registration, and token refresh follow the MCP spec (RFC 8414/7591/9728).
• Tools: submit_video, get_job_status, render_clip (the billed purchase moment), get_demo (free; works the moment you connect, no Cliphi account content needed).

Claude connector

In Claude, add a connector with the URL above. Claude opens the Cliphi sign-in page the first time; approve and then ask for clips from your video's link in plain words.

Generic client config

{
  "mcpServers": {
    "cliphi": {
      "url": "https://www.cliphi.com/api/mcp",
      "headers": { "Authorization": "Bearer chp_live_..." }
    }
  }
}

Tool errors carry the same human-ready message as the REST error envelope, with the stable code in a [error_code: ...] suffix.