mcp-lumiclip
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LUMICLIP_API_KEY | Yes | Your Lumiclip API key, get one at https://app.lumiclip.ai/developers | |
| LUMICLIP_API_URL | No | Base URL for the Lumiclip API | https://api.lumiclip.ai |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_clipsA | Start AI clip generation from a YouTube video. Returns a JSON object with project_id (string), status ('processing'), poll_url (string), and estimated_minutes (number). Processing is async -- use get_project_status to poll every 10-15 seconds, or provide a callback_url to receive a webhook POST when all clips are exported with download URLs. |
| get_project_statusA | Returns a JSON object with id, name, status (pending/processing/completed/completed_no_clips/failed), step, error, expected_clips, duration, created_at, and a clips array. Clips are sorted by score (highest first). Each clip has: id, title, duration, score, reason, clip_status (pending/exporting/completed/failed), download_url (string or null), quality, thumbnail_url, created_at, updated_at. The download_url is only available when clip_status is 'completed'. Poll every 10-15 seconds until project status is 'completed'. |
| list_projectsA | Returns a JSON object with projects (array), total, limit, and offset. Each project has: id, name, status, step, expected_clips, clips_count, duration, created_at. Use the status filter to find only completed or failed projects. |
| get_clipA | Returns a JSON object with full clip details: id, project_id, title, duration, score, reason, export_status, export_quality (720p/1080p), is_exported, video_url, video_url_720p, video_url_1080p, thumbnail_url, created_at, updated_at. |
| check_usageA | Returns a JSON object with plan (string), credits_remaining (number), credits_total (number), period_start (ISO date), and period_end (ISO date). Call this before generate_clips to confirm the user has enough credits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create-clips | Generate short-form clips from a YouTube video |
| check-credits | Check remaining Lumiclip credits and plan details |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: check_usage for credits, generate_clips for initiating generation, get_clip for retrieving a specific clip, get_project_status for polling progress, and list_projects for enumerating projects. No functional overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., generate_clips, get_project_status), making them predictable and intuitive.
Five tools is well-scoped for the server's purpose: credit checking, generation initiation, status polling, single clip retrieval, and project listing. Each tool serves a necessary function without excess.
Core workflow (check credits, generate, poll results, retrieve clips) is covered. Minor gaps like missing cancel operation or webhook management are present but not critical for basic usage.