videogenie-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIDEOGENIE_DATA_DIR | No | Absolute local data directory used to share project, storyline, and job state. Resolution is `--data-dir`, then `VIDEOGENIE_DATA_DIR`, then the OS-local application-data default. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Local stdio service using explicit project/storyline IDs and absolute media paths. Probe runs bounded inline and persists jobs/artifacts. Read failures before retrying. Tested with Python SDK mcp==2.3.0 and protocol 2026-07-28; other clients unverified.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| videogenie_capabilitiesA | Report implemented operations and real ffprobe dependency health; no media work. |
| videogenie_project_createB | Create a persistent project and initial storyline, or replay the original key. |
| videogenie_project_listA | List active projects; explicitly include archived records when needed. |
| videogenie_project_getA | Read an explicit project ID, including retained archived state. |
| videogenie_project_renameA | Rename an active project only at its current revision. |
| videogenie_project_archiveC | Archive at the current revision, preserving identity and history. |
| videogenie_project_restoreC | Restore the same archived project ID at the current revision. |
| videogenie_media_probeB | Run real ffprobe on an absolute local path with a durable bounded inline job. |
| videogenie_job_getB | Read a project-owned job, attempts and the SQLite JSON artifact with its SHA-256. |
| videogenie_job_resumeB | Resume recoverable work; reject live leases and reuse completed artifacts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Project lifecycle tools (create/list/get/rename/archive/restore) are clearly distinct, and media_probe is unique. The main overlap is between job_get and job_resume, both operating on jobs, though their descriptions distinguish reading metadata from resuming work.
All tools use the videogenie_ prefix and snake_case with a predictable resource_action pattern for projects and jobs. videogenie_capabilities is the lone exception, lacking a noun_verb form, but it remains understandable.
Ten tools is well within a focused range and each appears to serve a specific project, job, or diagnostic purpose. No obvious redundancy bloats the set.
The server is named videogenie-mcp but exposes no tool to start a video generation/render job, list jobs, or update project storylines. It covers project lifecycle, probing, and job inspection/resume, leaving the core generation workflow absent.