Server data from the Official MCP Registry
AI clips from long videos: analyze, clip, render and publish via the CutPro API.
AI clips from long videos: analyze, clip, render and publish via the CutPro API.
Remote endpoints: streamable-http: https://mcp.cut.pro
Valid MCP server (2 strong, 3 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.
Endpoint verified · Requires authentication · 2 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: CUTPRO_API_KEY
Environment variable: CUTPRO_WORKSPACE_ID
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
From the project's GitHub README.
A Model Context Protocol (MCP) server that turns long videos into viral clips with AI. It exposes the full CutPro API as tools, so an LLM can run the whole flow: analyze a video, clip the best moments, render the final MP4, and publish to TikTok, Instagram and YouTube.
list_clips is rating sorted, capped, and omits long signed URLs unless asked.Most clients use the same JSON. Add your API key under env:
{
"mcpServers": {
"cutpro": {
"command": "npx",
"args": ["-y", "@cutpro/mcp"],
"env": { "CUTPRO_API_KEY": "<your-api-key>" }
}
}
}
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
Add to claude_desktop_config.json (Settings, Developer, Edit Config):
{
"mcpServers": {
"cutpro": {
"command": "npx",
"args": ["-y", "@cutpro/mcp"],
"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 -e CUTPRO_API_KEY=<your-api-key>
Add to ~/.codex/config.toml:
[mcp_servers.cutpro]
command = "npx"
args = ["-y", "@cutpro/mcp"]
env = { "CUTPRO_API_KEY" = "<your-api-key>" }
Use the hosted server. Add a custom connector pointing to:
https://mcp.cut.pro
You authorize with your CutPro API key on a consent page (OAuth), so no local setup is needed.
The server is configured with environment variables.
| Variable | Description | Required |
|---|---|---|
CUTPRO_API_KEY | Your CutPro API key (Pro plan). | Yes (stdio) |
CUTPRO_WORKSPACE_ID | Selects the workspace for multi-workspace keys. | No |
CUTPRO_API_URL | Override the API base URL. Defaults to https://api.cut.pro/api/v1. | No |
| Variable | Description |
|---|---|
MCP_TRANSPORT=http / PORT | Serve Streamable HTTP at the root instead of stdio. |
MCP_OAUTH=1 | Enable the full OAuth 2.1 layer (discovery, DCR, PKCE) for browser clients. |
MCP_PUBLIC_URL | Public endpoint, e.g. https://mcp.cut.pro. Its origin becomes the OAuth issuer. |
MCP_REDIS_URL | Back OAuth state with Redis so it survives restarts and scales across instances. |
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
In OAuth mode the user authorizes with their own API key on a consent page; the access token maps server side to that key. Without MCP_REDIS_URL, an in-memory store is used (single instance, state lost on restart).
Each tool carries read-only / write / destructive annotations so clients can plan calls.
io.github.getcutpro/cutproMIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.