Skip to main content
mcpFirst-partyLow risk Safety Privacy
Invideo logo

Invideo MCP Server for Claude

Build video creation capabilities into your applications

HarnessClaude CodeCursorClaude Desktop

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://invideo.io/ai/mcp, https://github.com/JSONbored/awesome-claude/blob/main/content/mcp/invideo-mcp-server.mdx
Brand
Invideo
Brand domain
invideo.io
Brand asset source
brandfetch
Package URL
/downloads/mcp/invideo-mcp-server.mcpb
Package SHA256
ab826be403e238e55b55783ad32320578f6fa1f1010d07493d9a2469588b355e
Safety notes
Review generated video scripts, visuals, and exports before publishing or sharing them from production brand accounts.
Privacy notes
Prompts, uploaded media, brand assets, project metadata, and generated video content may be sent through tool calls.
Author
invideo
Claim status
unclaimed
Last verified
2025-09-18

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as first-party.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    Package marked verified.

    Done
  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

3 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

10 to clear

Platforms

3 listed

Difficulty

1/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

10 prerequisites to line up before setup. Have accounts and credentials ready first.

0/10 ready
Account & credentials5Network & hosting4General13 minutes

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 2 risk areas. Review closely: network access.

2 areas
  • SafetyExecution & processesReview generated video scripts, visuals, and exports before publishing or sharing them from production brand accounts.
  • PrivacyNetwork accessPrompts, uploaded media, brand assets, project metadata, and generated video content may be sent through tool calls.

Safety notes

  • Review generated video scripts, visuals, and exports before publishing or sharing them from production brand accounts.

Privacy notes

  • Prompts, uploaded media, brand assets, project metadata, and generated video content may be sent through tool calls.

Prerequisites

  • Invideo account (sign up at https://invideo.io if needed)
  • Invideo API key or OAuth credentials - get from Invideo account settings or Developer Hub
  • HTTP/SSE transport support (remote MCP server at https://mcp.invideo.io/sse)
  • Internet connection (remote Invideo API access required)
  • Understanding of video rendering/processing times (varies by video length, quality, and account tier)
  • Understanding of storage limits (varies by account tier - check account settings for current limits)
  • Understanding of export quotas (varies by account tier - check account settings for monthly export limits)
  • Understanding of supported media formats (MP4, MOV for video; JPG, PNG for images; check documentation for full list)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Understanding of video creation concepts (rendering, templates, voiceovers, subtitles, export formats, aspect ratios)

Schema details

Install type
package
Reading time
1 min
Difficulty score
1
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
ab826be403e238e55b55783ad32320578f6fa1f1010d07493d9a2469588b355e
Collection metadata
Estimated setup
3 minutes
Difficulty
beginner
Full copyable content
{
  "invideo": {
    "url": "https://mcp.invideo.io/sse",
    "transport": "sse"
  }
}

About this resource

Content

Transform your content creation workflow by connecting Claude to Invideo's AI-powered video platform. Generate professional videos from text prompts, edit existing videos programmatically, add voiceovers and music, create reusable templates, and export in multiple formats—all through natural language commands. Scale your video production, automate content creation, and deliver engaging visual content with AI-powered video generation.

Features

  • Generate videos from text prompts with AI-powered creation
  • Edit existing videos programmatically with timeline controls
  • Add voiceovers and background music with audio mixing
  • Create reusable video templates for consistent branding
  • Export videos in multiple formats and resolutions (MP4, MOV, various aspect ratios)
  • Add subtitles and captions with automatic transcription
  • Apply video effects, transitions, and filters
  • Manage video projects and media library programmatically
  • Advanced InVideo video creation and editing with AI-powered script generation, template library access, and automated video production
  • Batch operations support for efficient bulk video creation, editing, and rendering with automatic rate limit handling and retry logic
  • Real-time video synchronization capabilities with webhook integration support for monitoring video processing and triggering automated workflows

Use Cases

  • Generate marketing videos at scale with automated production
  • Create social media content automatically for multiple platforms
  • Produce educational video content with consistent formatting
  • Edit video presentations and training materials programmatically
  • Batch produce video variations with different text, images, or music
  • Create personalized video campaigns with dynamic content
  • Generate video summaries from blog posts or articles
  • Automate video production workflows with template-based creation
  • Build automated video production workflows that sync external systems with InVideo for real-time video creation and content management

Installation

Claude Code

  1. Get your Invideo API key from account settings or set up OAuth credentials (if using OAuth)
  2. claude mcp add --transport sse invideo https://mcp.invideo.io/sse
  3. Add INVideo_API_KEY to your environment or configuration if using API key authentication
  4. Verify installation: claude mcp list
  5. Test connection: claude mcp status invideo

Claude Desktop

  1. Get your Invideo API key from account settings or set up OAuth credentials (if using OAuth)
  2. Open your Claude Desktop configuration file (see configPath below)
  3. Add the Invideo server configuration with SSE transport pointing to https://mcp.invideo.io/sse
  4. Add INVideo_API_KEY to environment variables in configuration if using API key authentication
  5. Restart Claude Desktop
  6. Authenticate with your Invideo account when prompted (if using OAuth)

Requirements

  • Invideo account (sign up at https://invideo.io if needed)
  • Invideo API key or OAuth credentials - get from Invideo account settings or Developer Hub
  • HTTP/SSE transport support (remote MCP server at https://mcp.invideo.io/sse)
  • Internet connection (remote Invideo API access required)
  • Understanding of video rendering/processing times (varies by video length, quality, and account tier)
  • Understanding of storage limits (varies by account tier - check account settings for current limits)
  • Understanding of export quotas (varies by account tier - check account settings for monthly export limits)
  • Understanding of supported media formats (MP4, MOV for video; JPG, PNG for images; check documentation for full list)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Understanding of video creation concepts (rendering, templates, voiceovers, subtitles, export formats, aspect ratios)

Configuration

{
  "invideo": {
    "url": "https://mcp.invideo.io/sse",
    "transport": "sse"
  }
}

Examples

Create a 30-second product video

Common usage pattern for this MCP server

Ask Claude: "Create a 30-second product video"

Add subtitles to my video

Common usage pattern for this MCP server

Ask Claude: "Add subtitles to my video"

Generate a video from this blog post

Common usage pattern for this MCP server

Ask Claude: "Generate a video from this blog post"

Export video in 1080p MP4

Common usage pattern for this MCP server

Ask Claude: "Export video in 1080p MP4"

Create Video from Template

Create a new InVideo video from a template with custom script and media

// Create InVideo video from template
const video = await invideo.videos.create({
  template_id: "template-id",
  script: "Your video script text here",
  media: [
    {
      type: "image",
      url: "https://example.com/image.jpg",
    },
  ],
});

Security

  • OAuth authentication or API key for secure account access
  • Respect copyright for media assets (use licensed or royalty-free content)
  • Monitor storage usage limits to avoid service disruption
  • Check export quota restrictions based on account tier
  • Verify media file sources and licensing before use in videos
  • InVideo API keys and access tokens must be securely stored and never exposed in client-side code or public repositories - use environment variables and secure credential management
  • InVideo OAuth access tokens should be used for third-party integrations to ensure proper access control, token lifecycle management, and automatic token refresh
  • InVideo video IDs and project identifiers may expose content structure and media assets - ensure InVideo resource identifiers are kept private and not shared in public configurations
  • Rate limiting and API quota management are critical for InVideo MCP servers - implement proper rate limit handling, retry logic, and quota monitoring to prevent service disruption
  • InVideo webhook configurations and payloads may contain sensitive video metadata and media information - ensure webhook endpoints are properly secured with authentication and HTTPS encryption

Troubleshooting

Authentication error: could not authenticate user

Verify OAuth credentials are valid in Invideo account settings. For API key authentication, ensure the key is copied correctly and hasn't expired. Check username and password are correct if using basic auth. Ensure account isn't locked or suspended. Re-authenticate if needed or regenerate API key from account settings.

Video export or rendering queue taking too long

Check rendering queue status in Invideo dashboard. Large videos, high resolution, or complex effects take longer to process. Verify your account tier supports requested video length and quality settings. Free tier may have longer processing times. Contact support if queue appears stuck or exceeds expected processing time for your video specifications.

Storage limit exceeded when uploading media

Check storage usage in Invideo account settings. Delete unused videos, templates, or media assets to free space. Upgrade account tier for higher storage limits. Compress media files before upload to save space. Consider using external storage or linking to media instead of uploading when possible.

Unsupported media format error on upload

Verify media files are in supported formats: MP4, MOV for video; JPG, PNG, WEBP for images. Audio formats typically include MP3, WAV. Convert unsupported formats using video converter tools before uploading. Check file isn't corrupted and file size doesn't exceed account tier limits. Review Invideo documentation for complete list of supported formats.

InVideo MCP server authentication errors with API keys

Verify API key is valid and not expired. Check API key permissions match required operations. Ensure API key format is correct (Bearer token in Authorization header). For OAuth integrations, verify token refresh logic is working correctly.

InVideo rate limit errors when processing multiple video requests

Implement exponential backoff retry logic with jitter. Use InVideo API rate limit headers to monitor usage. Reduce concurrent requests. Cache frequently accessed template data. Check InVideo documentation for specific rate limits.

InVideo video creation or rendering failures

Check video file size limits and template availability. Verify account permissions allow video creation. Ensure network connectivity is stable. For large videos, use chunked upload API with resumable upload support.

InVideo MCP server connection timeouts or network errors

Check network connectivity and firewall settings. Verify InVideo API endpoints are accessible. Increase request timeout values. Implement connection pooling and retry mechanisms with exponential backoff.

Source citations

Add this badge to your README

Show that Invideo MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/invideo-mcp-server.svg)](https://heyclau.de/entry/mcp/invideo-mcp-server)

How it compares

Invideo MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).

Field

Build video creation capabilities into your applications

Open dossier

Upload, manage, transform, and analyze media assets in the cloud

Open dossier

Official MiniMax MCP server for using MiniMax text-to-speech, voice cloning, voice design, image generation, video generation, music generation, and media retrieval APIs from Claude and other MCP clients.

Open dossier

Source-install MCP server for controlling a local ComfyUI instance so Claude can generate, view, regenerate, manage, and publish image, audio, and video assets through workflow-backed tools.

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustDiffersPackage verifiedPackage verifiedPackage not verifiedPackage not verified
Source provenanceDiffersSource-backedNo submission linkSource-backedSource-backed
SubmitterDiffersoktofeesh1oktofeesh1
Install riskLow riskLow riskReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
BrandInvideo logoInvideoCloudinary logoCloudinaryMiniMax logoMiniMax
Categorymcpmcpmcpmcp
Sourcefirst-partyfirst-partysource-backedsource-backed
AuthorinvideoCloudinaryMiniMax-AIJoe Norton
Added2025-09-182025-09-182026-06-062026-06-06
Platforms
Claude CodeCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesReview generated video scripts, visuals, and exports before publishing or sharing them from production brand accounts.Use constrained Cloudinary credentials and review destructive or bulk asset operations before enabling media management actions.Most generation tools call MiniMax APIs and can incur account costs; only enable them for users who are authorized to spend from the MiniMax account. Voice cloning and voice design can create synthetic voices; obtain consent and rights for any source audio or identity-like voice prompt before use. Image-to-video, voice cloning, audio playback, and local output modes can read local files or URLs and send media to MiniMax APIs. Generated image, audio, video, and music outputs should be reviewed for policy, copyright, likeness, brand, and release constraints before publication. The API key and API host must match the selected region or requests can fail with authentication errors.ComfyUI MCP Server can submit prompts and workflows to a local ComfyUI instance, create generated media, poll jobs, cancel jobs, and publish assets into project directories. Generated images, audio, and video can contain unsafe, infringing, biased, misleading, or policy-sensitive content depending on prompts, models, LoRAs, and workflows. Publishing tools can copy, compress, convert, overwrite, and update manifest entries for assets, so verify target filenames and directories before use. Custom workflows can expose arbitrary parameters and may run heavy GPU workloads or fail if nodes, models, or paths are missing. Keep the server bound to local trusted clients unless you have added appropriate authentication and network controls.
Privacy notesPrompts, uploaded media, brand assets, project metadata, and generated video content may be sent through tool calls.Media assets, filenames, metadata, transformations, tags, delivery URLs, and account details may be sent through tool calls.Prompts, preview text, lyrics, source audio, first-frame images, uploaded files, generated media requests, and task IDs may be sent to MiniMax APIs and included in MCP client or model logs. MINIMAX_API_KEY must stay in environment variables or secret managers and should never be committed to MCP config files. Local output mode can write generated files under the configured base path, and returned file paths may reveal workstation directory structure to the MCP client. URL resource mode returns generated media URLs that may need access controls, retention review, and sharing policy before being pasted into chats or tickets.Prompts, negative prompts, generated media, workflow parameters, model names, job IDs, asset metadata, and publish paths can appear in MCP responses, logs, and model transcripts. Generated assets may be stored in ComfyUI output folders, the MCP asset registry, project publish directories, or manifests. Do not feed private images, brand assets, customer materials, or regulated media into workflows unless the local model environment is approved for that data. Review model and workflow licenses before publishing or redistributing generated assets.
Prerequisites
  • Invideo account (sign up at https://invideo.io if needed)
  • Invideo API key or OAuth credentials - get from Invideo account settings or Developer Hub
  • HTTP/SSE transport support (remote MCP server at https://mcp.invideo.io/sse)
  • Internet connection (remote Invideo API access required)
  • Cloudinary account (free or paid) from https://console.cloudinary.com/
  • Cloudinary Cloud Name (found in Cloudinary Console dashboard)
  • Cloudinary API Key (found in Cloudinary Console dashboard)
  • Cloudinary API Secret (found in Cloudinary Console dashboard)
  • MiniMax API key from the correct regional MiniMax platform.
  • MINIMAX_API_HOST set to the matching Global or Mainland endpoint for the API key.
  • uv or uvx available to run the Python package.
  • Optional MINIMAX_MCP_BASE_PATH when using local output mode for generated media files.
  • A local ComfyUI installation with required models and workflows.
  • Python and the repository requirements installed from the source checkout.
  • The MCP server launched from the cloned repository or with paths adjusted for your client.
  • Approved prompts, source assets, model licenses, and publish locations for generated media.
Install
claude mcp list && claude mcp status invideo
claude mcp add cloudinary --env CLOUDINARY_CLOUD_NAME=YOUR_CLOUD_NAME --env CLOUDINARY_API_KEY=YOUR_KEY --env CLOUDINARY_API_SECRET=YOUR_SECRET
uvx minimax-mcp
git clone https://github.com/joenorton/comfyui-mcp-server && cd comfyui-mcp-server && pip install -r requirements.txt
Config
{
  "mcpServers": {
    "invideo": {
      "url": "https://mcp.invideo.io/sse",
      "type": "sse"
    }
  }
}
{
  "mcpServers": {
    "cloudinary": {
      "env": {
        "CLOUDINARY_API_KEY": "${CLOUDINARY_API_KEY}",
        "CLOUDINARY_API_SECRET": "${CLOUDINARY_API_SECRET}",
        "CLOUDINARY_CLOUD_NAME": "${CLOUDINARY_CLOUD_NAME}"
      },
      "url": "https://mcp.cloudinary.com/",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "minimax": {
      "command": "uvx",
      "args": [
        "minimax-mcp"
      ],
      "env": {
        "MINIMAX_API_KEY": "insert-your-api-key-here",
        "MINIMAX_API_HOST": "https://api.minimax.io",
        "MINIMAX_API_RESOURCE_MODE": "url"
      },
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "comfyui-mcp-server": {
      "command": "python",
      "args": ["server.py", "--stdio"],
      "env": {
        "COMFYUI_URL": "",
        "COMFY_MCP_WORKFLOW_DIR": "",
        "COMFYUI_OUTPUT_ROOT": "",
        "COMFY_MCP_ASSET_TTL_HOURS": "24"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.