Koskamo

Vidova MCP

The Vidova MCP server enables AI agents to interact with the Vidova agentic video editor. It allows users to upload footage or start from a prompt, instructing the agent to cut, trim, arrange clips, add captions, generate media, and export projects on a real timeline.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Vidova MCP logo, by VidovaOAuth sign-inEndpoint checked 2026-10-26Operated by Vidova
MCP endpoint (Streamable HTTP)
https://mcp.vidova.ai/mcp
Vendor documentation

What you can do with it

  • Edit videos by describing desired cuts and captions
  • Generate vertical clips for TikTok and Reels
  • Add animated captions, titles, and logo intros
  • Export projects to MP4 or editing software formats

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http vidova-mcp https://mcp.vidova.ai/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add vidova-mcp --url https://mcp.vidova.ai/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable vidova-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "vidova-mcp": {
      "url": "https://mcp.vidova.ai/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "vidova-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.vidova.ai/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start vidova-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "vidova-mcp": {
      "type": "http",
      "url": "https://mcp.vidova.ai/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http vidova-mcp https://mcp.vidova.ai/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "vidova-mcp": {
      "url": "https://mcp.vidova.ai/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "vidova-mcp": {
      "serverUrl": "https://mcp.vidova.ai/mcp"
    }
  }
}

Ground your agent in cited data

Vidova MCP gives your agent tools. Koskamo gives it reviewed, cited facts to check its answers against. Add it as a second MCP server; public reads need no API key.

Do you run Vidova MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing