# lumiclip [Health: Active]

**Category:** 🎥 Multimedia Process  
**Repository:** https://github.com/lumiclip/lumiclip-mcp-server  
**GitHub Stars:** 0  
**npm Downloads (last month):** 139  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/lumiclip

## Description
Turn YouTube videos into short-form clips from any AI assistant

## Tools
Capabilities this server exposes over MCP:

- **generate_clips** — Start clip generation from a YouTube URL. Returns a `project_id` right away.
- **get_project_status** — Check progress and get clips when ready. Clips are sorted by score (best first).
- **list_projects** — List your projects with status and clip counts.
- **get_clip** — Get full details for a single clip.
- **check_usage** — See your plan, remaining credits, and usage.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "lumiclip": {
    "command": "npx",
    "args": ["-y","@lumiclip/mcp-server"],
    "env": {
      "LUMICLIP_API_KEY": "",
      "LUMICLIP_API_URL": ""
    }
  }
}
```

**Requires environment variables:** `LUMICLIP_API_KEY`, `LUMICLIP_API_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the lumiclip MCP server does

The lumiclip MCP server connects an MCP client to Lumiclip’s video-processing API. It accepts a full YouTube URL, starts a clip-generation project, and returns a project ID immediately. Lumiclip processes the source video, identifies highlights, creates vertical 9:16 clips, adds subtitles, and exposes finished media through download and thumbnail URLs.

The service is suited to workflows that turn long YouTube recordings into short-form content. Optional start and end times allow a request to target only part of a video. Results include clip titles, durations, scores, explanations, export status, and available video qualities.

## How it works

Call `generate_clips` with a YouTube URL. The response includes a `project_id`, current status, a polling path, and an estimated processing time. An agent can then call `get_project_status` every 10–15 seconds until the project completes. Completed clips are ordered by score, with the highest-scoring result first.

Instead of polling, pass a `callback_url` to receive a POST when processing finishes. Completion and failure events include the project ID and result details. Lumiclip retries a callback up to three times if the receiving server does not respond. Optional callback signature verification uses the `X-Lumiclip-Signature` header and an HMAC-SHA256 value derived from the API key.

Projects move through pending, processing, and completed states, with additional outcomes for projects that produce no clips or fail. Individual clips also have export states; their download URL becomes available after export completes.

## Setup and configuration

Create an API key through Lumiclip’s developer page, then run the package with `npx`:

```bash
LUMICLIP_API_KEY=sk_live_... npx @lumiclip/mcp-server
```

For Claude Desktop or Cursor, add the server command and API key to the relevant MCP configuration. The package reads `LUMICLIP_API_KEY`, which is required. `LUMICLIP_API_URL` is optional and defaults to `https://api.lumiclip.ai`.

A remote Streamable HTTP endpoint is available at `https://mcp.lumiclip.ai/mcp`. Remote requests use an `Authorization: Bearer` header.

## Tools and capabilities

- `generate_clips`: Starts processing and accepts optional segment boundaries and a callback URL.
- `get_project_status`: Retrieves processing progress and completed clips.
- `list_projects`: Lists projects, with status filtering and a configurable limit from 1 to 100.
- `get_clip`: Returns detailed metadata and video URLs for one clip.
- `check_usage`: Reports the current plan, total credits, remaining credits, and billing period.

## Limitations and notes

Requests require a valid YouTube URL and an API key. Insufficient credits, invalid URLs, authentication failures, rate limits, unavailable videos, and server errors can prevent processing. A completed project may contain no clips. The lumiclip MCP server returns links to exported media; the material does not describe local file storage or editing controls beyond the documented generation options.

_Full upstream README: https://allmcps.com/mcp/lumiclip/readme_