long-video-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIDEO_MCP_DATA | No | Environment variable to change the location where projects are stored. Projects are stored in ~/.long-video-mcp by default. | ~/.long-video-mcp |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| plan_structureA | Plan the segment structure (hook, intro, chapters, outro) of a long-form video for a target duration. Returns time ranges and retention advice. Does not save anything. |
| create_projectA | Create and save a long-video project with an auto-generated structure. Use the returned project name in other tools. |
| list_projectsB | List all saved video projects. |
| rename_segmentB | Give a segment (e.g. 'Chapter 2') a real title. Titles are used for YouTube chapter timestamps. |
| save_scriptA | Save (or replace) the narration script of one segment and report its estimated speaking time versus the planned time. |
| analyze_scriptB | Analyze any narration text: word count, estimated duration, and pacing warnings (very long sentences or paragraphs). |
| project_reportB | Report progress of a project: which segments have scripts, estimated total runtime versus the target. |
| generate_timestampsA | Generate YouTube chapter timestamps for a project. Uses actual script lengths when available, otherwise planned times. |
| shot_listB | Split a narration script into visual beats (a new visual every N seconds) with timecodes, so a long video never stays on one static shot. |
| production_checklistA | Return a stage-by-stage production checklist for a long-form video (pre-production, recording, editing, publishing). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| write_chapter_script | Template: write the narration for one segment of a project, respecting its time budget. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools target clearly distinct actions: planning (plan_structure), persistence (create_project, list_projects), scripting (save_script, analyze_script), and reporting (project_report, generate_timestamps). The main overlap is plan_structure versus create_project, both producing segment structures, distinguished only by whether they save; an agent could plausibly reach for the wrong one. rename_segment and save_script are close in that both edit segment content, but their descriptions separate them adequately.
The dominant pattern is verb_noun snake_case (plan_structure, list_projects, create_project, rename_segment, save_script, analyze_script, generate_timestamps). However, three tools break it with noun-only names: project_report, shot_list, and production_checklist. The set is still readable and mostly predictable, but the mixed convention is noticeable.
Ten tools is a well-scoped size for a long-form video planning server. Each tool maps to a distinct stage of the workflow—planning, project persistence, scripting, analysis, reporting, and production guidance—and none feels redundant filler.
The surface covers the core lifecycle: plan a structure, persist a project, title segments, write and analyze scripts, report progress, generate timestamps, and build shot lists and production checklists. Gaps are modest—there is no delete_project or project rename, and no way to remove or list individual segments explicitly, but these are workable around the create/list/report tools.