clipici-mcp

An MCP server for Clipici — turn long videos into captioned, viral-ready short clips (with correct Romanian diacritics) from any MCP client: Claude Code, Claude Desktop, Cursor, and more.

What it does

The server wraps the Clipici REST API as MCP tools:

It also exposes read-only resources (clipici://jobs, clipici://jobs/{id}, clipici://clips/{id}) and a guided prompt make_viral_clips.

Get an API key

In the Clipici dashboard → Setări → Chei API, generate a key (clpc_live_…). It's shown once — copy it.

Use it (local / stdio)

Add to your MCP client config (Claude Code: ~/.claude.json or project .mcp.json; Claude Desktop: claude_desktop_config.json):

{
  "mcpServers": {
    "clipici": {
      "command": "uvx",
      "args": ["clipici-mcp"],
      "env": { "CLIPICI_API_KEY": "clpc_live_your_key_here" }
    }
  }
}

CLIPICI_API_URL defaults to https://api.clipici.ro. For local development against your own backend, add "CLIPICI_API_URL": "http://localhost:8000".

Then ask your agent: "Use Clipici to turn ./talk.mp4 into viral clips, wait for it, and download the top clip to ./clips/."

Hosted / remote (Streamable-HTTP)

The same server can run as a remote MCP at https://mcp.clipici.ro — point a remote-MCP-capable client at it and authenticate with Authorization: Bearer clpc_live_…. Note: local-file tools (file_path, dest_path) only work in stdio mode; with the hosted server, pass a public url and use the returned download URL.

Environment variables

Develop & test

cd mcp
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
pytest -q                      # unit tests (no backend needed)

# Interactive tool testing:
CLIPICI_API_KEY=clpc_live_… npx @modelcontextprotocol/inspector uvx clipici-mcp

# Opt-in end-to-end smoke against a local backend:
CLIPICI_E2E=1 CLIPICI_API_URL=http://localhost:8000 \
  CLIPICI_API_KEY=clpc_live_… CLIPICI_E2E_VIDEO=./sample.mp4 pytest -q tests/test_e2e_smoke.py