Video Editing AI MCP vs Vidocu

A side-by-side look at the Video Editing AI MCP and Vidocu MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Video Editing AI MCP logoVideo Editing AI MCPMultimedia Process · Local subprocess (stdio)Video Editing Ai MCP server. Tools: split scenes, generate subtitles, thumbnail data. Built by MEOK41FairAuth: not declared
V
VidocuMultimedia Process
AI Knowledge Platform: turn videos, PDFs, and slides into subtitles, voiceovers, and documentation42FairAuth: not declared

Verdict: choose Video Editing AI MCP for multimedia process work as a local process; choose Vidocu for multimedia process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Video Editing AI MCP logoChoose Video Editing AI MCP when

  • You need dedicated capabilities in the Multimedia Process domain.
  • You prefer a local stdio subprocess transport.
Explore Video Editing AI MCP

V
Choose Vidocu when

  • You need dedicated capabilities in the Multimedia Process domain.
Explore Vidocu

Feature & specification comparison

Rows where the two servers differ are marked.

SpecVideo Editing AI MCP logoVideo Editing AI MCP
V
Vidocu
CategoryMultimedia ProcessMultimedia Process
Quality signal41/100 · Fair42/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars0—
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Video Editing AI MCP tools

No tool names declared yet. Check the project README from the listing page.

Vidocu tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Video Editing AI MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "video-editing-ai-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "meok-setup"
      ]
    }
  }
}

Vidocu

No confirmed install command for Vidocu yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Video Editing AI MCP is categorized under Multimedia Process and uses a local stdio subprocess. Vidocu belongs to Multimedia Process and uses an install path we have not confirmed yet. Pick Video Editing AI MCP for multimedia process work and Vidocu for multimedia process.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Vidocu has no confirmed install command yet — follow its own setup instructions.

Video Editing AI MCP has no declared pricing — check the project's own site. Vidocu has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add video-editing-ai-mcp and vidocu as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Video Editing AI MCP has a quality signal of 41/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Vidocu has 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.