AI Video Pipeline MCP Server
An MCP server that powers an AI video production pipeline for algorithm-explanation YouTube videos, designed to run alongside Claude Desktop.
How It Works
Claude Desktop is the AI. This server provides structured tools and prompt templates — no external AI API calls, no API keys required.
When you call a tool (e.g. generate_script), it:
- Validates your inputs
- Assembles a rich, domain-specific prompt using carefully crafted templates
- Returns a prompt packet to Claude Desktop
Claude reads the packet and generates the output (script, scene list, image prompt, Python code) directly in the conversation.
Pipeline
1. generate_script → Full narration script with visual cues
2. [record voiceover] → Human step — export timestamped transcript
3. plan_scenes → Visual scene list with timestamps
4. generate_image_prompt → Whisk/Midjourney prompt per image scene
5. generate_video_compositor → Python script that assembles the final video
Tools
| Tool | Description |
|---|---|
generate_script |
Write a complete audio-first narration script |
plan_scenes |
Convert a timestamped transcript into a scene storyboard |
generate_image_prompt |
Generate a Whisk/AI image prompt for a scene |
generate_video_compositor |
Generate a Python video compositor script |
Installation & Claude Desktop Setup
Prerequisites
- Python 3.12+
- uv package manager
- Claude Desktop
Install
# Clone the repo
git clone https://github.com/YOUR_USERNAME/mcp_deployment.git
cd mcp_deployment
# Install dependencies
uv sync
Configure Claude Desktop
Add this to your claude_desktop_config.json (usually at %APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": {
"ai-video-pipeline": {
"command": "uv",
"args": [
"--directory",
"C:/Proj/DD/mcp_deployment",
"run",
"ai-video-mcp"
]
}
}
}
Note: Change the
--directorypath to wherever you cloned the repo.
Restart Claude Desktop. The 4 tools will appear in the tool list.
Testing Without Claude Desktop
Use the MCP Inspector to test tools interactively:
mcp dev src/mcpserver/server.py
Open http://localhost:5173, select a tool, fill in the inputs, and click Run.
Re-publishing (GitHub)
To update the server after making changes:
1. Bump the version
In pyproject.toml, increment version:
version = "0.2.1" # or 0.3.0 for bigger changes
2. Build
uv build
This produces dist/ai_video_pipeline_mcp-X.Y.Z-py3-none-any.whl.
3. Commit and push
git add -A
git commit -m "chore: bump to vX.Y.Z — describe your changes"
git push origin main
4. Update Claude Desktop config (if path changed)
Restart Claude Desktop to pick up the new version. Since you're running from source via uv run, this happens automatically — no reinstall needed.
Optional: Install from GitHub directly
If you want to install the server as a package from GitHub (instead of running from source):
uv pip install git+https://github.com/YOUR_USERNAME/mcp_deployment.git
Then use ai-video-mcp as the command in claude_desktop_config.json (no --directory needed).
Project Structure
src/mcpserver/
├── server.py # FastMCP server — registers all tools
├── __main__.py # Entry point (ai-video-mcp command)
├── tools/
│ ├── script_generator.py # Tool 1: generate_script
│ ├── scene_planner.py # Tool 2: plan_scenes
│ ├── image_prompt_generator.py # Tool 3: generate_image_prompt
│ └── animation_generator.py # Tool 4: generate_video_compositor
└── utils/
└── schemas.py # Pydantic input schemas
Metadata
Release files for ai-video-pipeline-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ai_video_pipeline_mcp-0.2.0.tar.gz | 20.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ai_video_pipeline_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 45.5 kB
Release files / ai_video_pipeline_mcp-0.2.0.tar.gz
| Download URL | ai_video_pipeline_mcp-0.2.0.tar.gz |
|---|---|
| Size | 20.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5c5c66c7306aebc3544fb7376213128e78f5c42de5e9a5d295f518f14dfd86b
|
|
BLAKE2b-256 checksum How to use checksums |
2510c25cb3c2a8e04f0b70fdf46c13d1dd0e7f20b7de3431d346b0cc4df0eff5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.5 {"installer":{"name":"uv","version":"0.10.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / ai_video_pipeline_mcp-0.2.0-py3-none-any.whl
| Download URL | ai_video_pipeline_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 25.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7cbce872f3376dc72afa4fc79cc0813d97a27e686255082ea8670739cc667f7a
|
|
BLAKE2b-256 checksum How to use checksums |
2b2142a04d4e37811b21bc23cc8a3c9f70e93e04e9e61e6d045c789a1d32c19e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.5 {"installer":{"name":"uv","version":"0.10.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for ai-video-pipeline-mcp 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.