AutoKeren MCP

What AutoKeren MCP MCP server does

AutoKeren MCP MCP server provides agent-accessible video production workflows through the hosted endpoint at https://mcp.autokeren.com. It covers the main stages of producing a video: creating a project, loading scenes, generating or attaching media, rendering an MP4, checking the result, and reviewing usage. The service is operated remotely; the repository serves as documentation and onboarding material rather than the live runtime.

The workflow can combine generated images, narration, video clips, and sourced YouTube footage. Agents can also prepare upload metadata, reuse assets from the service’s library, and request signed upload URLs for files that exceed ordinary upload limits. The README describes a free tier for selected Cloudflare-based script, image, and text-to-speech models, while other models and video generation use credits.

How it works

Clients connect over Streamable HTTP and authenticate each request with an API key in an Authorization: Bearer header. An agent can first read the published skill guide at https://mcp.autokeren.com/skill.md for the service’s workflow instructions, then call MCP tools such as get_workflow, create_project, load_scenes, generate_assets, and render_video.

Several operations are asynchronous. Premium Remotion rendering returns a polling identifier, which the client passes to render_remotion_result to obtain the result. The incremental Remotion path renders individual slides before they are stitched together, allowing each slide to be checked separately. Media returned by the service is verified in R2, and attached media is preserved when assets are generated.

Setup and configuration

Create an API key through the AutoKeren settings page, then register the hosted URL in an MCP client. Claude Code uses an HTTP transport registration with the Bearer header. Cursor and Windsurf can use the same URL and header in their MCP JSON configuration. The README also provides a JSON-RPC curl example for clients that can make HTTP requests directly.

No local server process or repository build is required for the hosted service. The key should be treated as a secret and supplied through the client’s header configuration rather than embedded in prompts.

Tools and capabilities

The documented tool groups support:

• Pipeline management, scene loading, asset generation, rendering, render verification, error inspection, usage checks, and asset-library browsing.
• Image, speech, and video-clip generation, including asynchronous polling for some media providers.
• YouTube search, download, shot indexing, frame extraction, and scene-specific video cutting.
• Vision checks, media analysis, full-video checks, and production reviews.
• Packaging suggestions, presigned uploads, and Remotion preparation.
• Character sheets, last-frame extraction, and cinematic-film script generation.

AutoKeren MCP MCP server also supports a 9:16 project aspect ratio for Shorts and a 4k render resolution according to the README. Voice selection uses a documented catalog of verified voices across English, German, and multilingual options.

Limitations and notes

The service requires network access to the hosted endpoint and an API key. Paid generation and premium rendering consume credits; current model prices are exposed through list_models, and credits can be added through the studio or topup_credits. Video clip generation is not listed in the free tier.

The README contains different tool-count badges and headings, so the exact total should be confirmed from the live service rather than inferred from those counts. AutoKeren MCP MCP server supports the MCP protocol versions listed in its documentation and is deployed on Cloudflare Workers and Containers. The material does not describe a local deployment option or a self-hosted runtime.