Skip to main content
Glama
long-video-mcp

long-video-mcp

by Ehmad9
README.md
# long-video-mcp

An MCP (Model Context Protocol) server that helps Claude plan, script, pace and package
long-form videos (10 to 60+ minutes).

## Tools

| Tool | What it does |
|---|---|
| `plan_structure` | Splits a target duration into Hook, Intro, Chapters and Outro, with advice for each part (saves nothing) |
| `create_project` | Creates and saves a project with an auto-generated structure |
| `list_projects` | Lists saved video projects |
| `rename_segment` | Gives a segment a real title (used for YouTube chapters) |
| `save_script` | Saves the narration of a segment and compares its speaking time with the planned time |
| `analyze_script` | Analyzes any text: word count, duration, and long sentences or paragraphs |
| `project_report` | Progress report: scripted segments and total runtime versus the target |
| `generate_timestamps` | Generates YouTube chapter timestamps (`0:00 ...`) |
| `shot_list` | Splits a script into visual beats, with a new visual every N seconds |
| `production_checklist` | Checklist for pre-production, recording, editing and publishing |

**Resources:** `project://<project-name>` returns the full project data (JSON).
**Prompts:** `write_chapter_script` is a template for writing a segment within its time budget.

## Install

Requires [Node.js](https://nodejs.org) (LTS) and [Claude Desktop](https://claude.ai/download).

```bash
git clone https://github.com/Ehmad9/long-video-mcp.git
cd long-video-mcp
npm install
npm run build        # produces build/index.js
npm test             # starts the server and calls every tool
```

## Connect to Claude Desktop

Open `Settings → Developer → Edit Config` and add the server, using the absolute path to
`build/index.js`:

```json
{
  "mcpServers": {
    "long-video": {
      "command": "node",
      "args": ["/absolute/path/to/long-video-mcp/build/index.js"]
    }
  }
}
```

On Windows use forward slashes, for example `C:/long-video-mcp/build/index.js`.
Then fully quit Claude (from the system tray) and open it again.

Projects are stored in `~/.long-video-mcp` by default. Set the `VIDEO_MCP_DATA`
environment variable to change the location.

## Example prompts

- "Create a 25-minute video project about the history of coffee"
- "Write the script for chapter 3, save it, and tell me if it is too long"
- "Generate YouTube chapters for the project"
- "Make a shot list for this script"

## Notes

- Never use `console.log` inside the server, because it corrupts the stdio channel. Use `console.error`.
- The default narration speed is 150 words per minute. For slower speech, set `wpm` to 120-140.

## Contributing and security

Pull Requests are welcome, but **every change is reviewed by hand before merging**, because this
server runs on users' computers. See [CONTRIBUTING.md](CONTRIBUTING.md).

## License

MIT

TDQS

B3.4/5.0

Scored across 10 tools

Disambiguation4/5

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.

Naming Consistency3/5

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.

Tool Count5/5

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.

Completeness4/5

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.