Parallel scene generation for video explainer pipeline via Claude Agent SDK + FastMCP
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"video-agent-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# video-agent-mcp Generate Remotion scene components concurrently from an existing explainer script. The server reads project files, sends scene prompts through the Claude Agent SDK, and writes TSX plus a scene index. Use the explainer server and upstream renderer to prepare inputs, preview scenes, and render the video. Two tools are available: `agent_generate_scenes` and `agent_generate_single_scene`. Repository links point to the published source release. For the exact source and bundled README of a registry version, use its source archive on [PyPI](https://pypi.org/project/video-agent-mcp/#files). ## Install and configure You need Python 3.11 or newer, [uv](https://docs.astral.sh/uv/), an existing explainer project, and supported Agent SDK authentication. The SDK bundles its CLI; follow its [authentication guide](https://code.claude.com/docs/en/agent-sdk/overview) for Anthropic API or supported cloud-provider credentials. From this package directory in a source checkout: ```sh uv sync --locked --extra dev uv run --locked video-agent-mcp ``` The command starts a stdio MCP server. Register it in your client's configuration rather than expecting a terminal UI. For Claude Code, add this entry to the appropriate `mcpServers` object, replacing the absolute checkout path: ```json { "video-agent": { "command": "uv", "args": [ "run", "--locked", "--directory", "/absolute/path/to/video-research-mcp/packages/video-agent-mcp", "video-agent-mcp" ] } } ``` To use a registry release, register `uvx` with `video-agent-mcp==<published-version>` instead. Confirm that exact version is published first. The core npm installer does not register this companion. Configuration comes from the process environment and `~/.config/video-research-mcp/.env`; nonempty process values take precedence. Use the same project location as the explainer server: ```dotenv EXPLAINER_PATH=/absolute/path/to/video_explainer # Optional: projects outside EXPLAINER_…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.