Cutpro MCP Server

CutPro MCP

A Model Context Protocol (MCP) server for AI images, videos, personas and clips. It exposes the full CutPro API as tools, so an LLM can:

• Generate images and videos with any top model: Veo, Kling, Seedance, Wan, MiniMax, Nano Banana, GPT Image, Seedream and more, from a prompt or from reference images, with each model's live price.
• Create AI personas: realistic people that stay consistent across photos and videos, then swap them into any video while scene, camera, motion and sound stay.
• Clip long videos and live streams: find the best moments and render the final MP4.
• Post and schedule: publish any clip, generated video or persona video to TikTok, Instagram, YouTube, Facebook, Threads, LinkedIn, Pinterest and Bluesky, now or at a set time.
• Transcribe: any audio or video into timed captions (SRT, VTT, text or JSON).

Key features

• Always in sync. Every v1 endpoint is a tool, generated from the live API spec: image and video generation, personas, workspace, balance, videos and uploads, clipping, clips, channel and live monitoring, templates, renders, transcriptions, posts and connections.
• Runs everywhere. stdio for local clients (Claude Code, Cursor, Claude Desktop, Windsurf, VS Code, Cline, Zed) and a hosted Streamable HTTP endpoint with OAuth for ChatGPT and Claude.ai.
• Latest protocol. Speaks MCP 2026-07-28 (stateless, server/discover, cacheable lists, multi round-trip requests) and every earlier revision, on the same endpoint.
• Results you can watch. Clients that support MCP Apps show generated images and videos, personas, clips and renders as an inline player that follows a job until it is ready, with buttons to open it in CutPro, animate an image or schedule a post.
• Asks before it spends. On clients that support elicitation, every call that charges credits shows the price and waits for the user's confirmation before anything is charged.

Getting started

Requirements

• Node.js 18 or newer.
• A CutPro account (any plan) and an API key. Generate one at cut.pro/studio/me/api-keys.
• An MCP-compatible client.

Standard config

Most clients use the same JSON. Add your API key under env:

{
	"mcpServers": {
		"cutpro": {
			"command": "npx",
			"args": ["-y", "@cutpro/mcp@latest"],
			"env": { "CUTPRO_API_KEY": "<your-api-key>" }
		}
	}
}

Install

After installing via a button, add your CUTPRO_API_KEY to the server's env.

claude mcp add cutpro --env CUTPRO_API_KEY=<your-api-key> -- npx -y @cutpro/mcp@latest

Add to claude_desktop_config.json (Settings, Developer, Edit Config):

{
	"mcpServers": {
		"cutpro": {
			"command": "npx",
			"args": ["-y", "@cutpro/mcp@latest"],
			"env": { "CUTPRO_API_KEY": "<your-api-key>" }
		}
	}
}

Add the standard config above to the client's MCP settings (mcp.json / mcpServers).

Open the MCP Servers panel, choose Configure, and add the standard config above.

gemini mcp add cutpro npx -y @cutpro/mcp@latest -e CUTPRO_API_KEY=<your-api-key>

Add to ~/.codex/config.toml:

[mcp_servers.cutpro]
command = "npx"
args = ["-y", "@cutpro/mcp@latest"]
env = { "CUTPRO_API_KEY" = "<your-api-key>" }

Use the hosted server. Add a custom connector pointing to:

https://mcp.cut.pro

You sign in to cut.pro, pick the workspace and approve the connection, so no API key and no local setup are needed. Any CutPro plan can connect; jobs use the workspace's credits. Disconnect at any time in Settings, under Connected apps.

The plugin bundles the hosted server with a skill that teaches Claude the CutPro workflows:

claude plugin marketplace add getcutpro/mcp
claude plugin install cutpro@cutpro

Updates

Every install stays current on its own:

• Hosted (https://mcp.cut.pro, the Claude plugin and the ChatGPT app): always the latest release, nothing to do.
• Local (npx -y @cutpro/mcp@latest): on start the server checks npm and, when a newer release exists, hands the session to it. This works even for a pinned version or a stale npx cache. Set CUTPRO_MCP_AUTO_UPDATE=0 to stay on the installed version; the server then tells the model an update is available.
• Tools: new API endpoints show up as tools within ten minutes, without any release.

Every release is listed with its notes in Releases and CHANGELOG.md.

Configuration

The server is configured with environment variables.

MCP_TRANSPORT=http PORT=8787 MCP_OAUTH=1 \
MCP_PUBLIC_URL=https://mcp.cut.pro MCP_REDIS_URL=redis://127.0.0.1:6379 \
npx -y @cutpro/mcp@latest

In OAuth mode the user signs in on cut.pro and approves the app there; cut.pro creates a key for that app and workspace, and the access token maps server side to it. Clients can register dynamically (DCR) or present a Client ID Metadata Document (CIMD). Without MCP_REDIS_URL, an in-memory store is used (single instance, state lost on restart).

Tools

The tools are built from the API's own OpenAPI spec (/api/v1/openapi.json), so they always match the API reference: one tool per endpoint, named after its operationId in snake case (analyzeVideo is analyze_video, createSubmission is create_submission), with the endpoint's own parameters, descriptions and responses. A new endpoint becomes a tool within ten minutes of reaching the API, with no new release of this package.

The usual flows:

• Image or video: list_generation_models, create_generation with the agreed price, get_generation until it is ready. Pass a ready image's output.image_id to animate it.
• Persona: get_persona_catalog, create_persona, get_persona until its photo is ready, save_persona, then quote_persona_swap and create_persona_video to put it in a video.
• Clips: analyze_video, create_submission, get_submission until it completes, list_clips, render_clip, get_render and download_render.

Annotations come from the spec too: GET is read-only, PUT, PATCH and DELETE are destructive, and a route declares more in its x-mcp extension (spending credits, publishing to a social network, reaching an arbitrary public URL). Routes that need a file uploaded from disk are listed only by the local (stdio) server, since a chat client cannot send bytes.

All tools

90 tools and 5 prompts, generated from the live API spec and the server.

Prompts

Ready-made requests your client offers as shortcuts (the / menu in Claude).

Workspace

Balance

Videos

Submissions

Clips

Renders

Connections

Monitoring

Posts

Templates

Transcriptions

Personas

Generations

Links

• Docs: cut.pro/docs/api-reference/mcp
• npm: @cutpro/mcp
• MCP Registry: io.github.getcutpro/cutpro
• Releases: github.com/getcutpro/mcp/releases · CHANGELOG.md
• Contributing: CONTRIBUTING.md · Security: SECURITY.md · Code of Conduct

License

MIT