Videoslash API

MCP Server

Connect AI coding agents to Videoslash via the Model Context Protocol.

MCP Server

The Videoslash MCP server exposes your account, scripts, and Creative Studio through the Model Context Protocol (MCP). Connect it from Claude Code, Cursor, Codex CLI, or OpenCode to generate scripts, images, and videos without leaving your agent session.

Server URL

https://www.videoslash.com/api/mcp

Authentication

The MCP server uses the same API keys as the public REST API. Create a key in Account settings under Developers and pass it as a Bearer token in your MCP client configuration.

Each key's scopes control which tools the agent can see:

ScopeTools
readAccount, credits, Creative Studio model catalog
scripts:generateTitle and script generation
creative:generateCreative Studio generations and media uploads

A key only lists tools it is allowed to use. Enable Allow script generation and Allow Creative Studio generation when creating a key for write access.

Quick start

  1. Create an API key with the scopes you need.
  2. Add the MCP server to your agent — see Configuration.
  3. Ask your agent to check credits, list models, or start a generation.

Example prompts:

  • "Check my Videoslash credit balance."
  • "List fast video models and generate a 5-second product clip."
  • "Generate a script title about ancient civilizations."

Workflow examples

Chain a prior generation as input

  1. Call create_creative_generation to produce an image.
  2. Poll get_creative_generation until status is completed.
  3. Pass the returned outputUrl in mediaUrls when calling create_creative_generation again with a video model.

The agent can reuse any completed CDN outputUrl from list_creative_generations the same way.

Compare models on the same prompt

  1. Call list_creative_models with filters (for example category: Fast).
  2. Call create_creative_generation multiple times with different modelId values and the same prompt.
  3. Poll each generation and compare the outputUrl results.

Async generations

Creative Studio tools mirror the REST API: create_creative_generation returns immediately with a generation id. Poll get_creative_generation until status is completed or failed. Completed outputs expose a CDN URL on cdn.videoslash.com.

Local file uploads

MCP does not transfer file bytes. For image-to-image or video reference inputs from disk:

  1. Call request_creative_media_upload with file metadata.
  2. Upload bytes with curl -T to the returned uploadUrl using requiredHeaders.
  3. Pass the uploadId in mediaUploads when calling create_creative_generation.

See the Creative Studio API guide for the same presigned upload flow over REST.

Tool reference

Generated tool pages live under Tools. Run pnpm docs:generate after changing tool definitions in lib/mcp/tools.ts.

On this page