Documentation · v0.1 beta · Last updated May 1, 2026

Connect your agent in two minutes.

One command works in every MCP-compatible client. Copy the snippet for yours, paste it in the config file, restart — done. Inside the app, Settings → Connect AI Agents writes the config for you.

Install the app first·Stuck? Get help

Before you configure

The one command every client runs

Every client below points at the same command with the same args. If your client isn't listed but speaks MCP over stdio, use this:

MCP command

shell

npx -y @videoedit-mcp/bridge

Install VideoEdit MCP

Run the install script from /download.

Launch and sign in

Open the app, sign in, and leave it running. Your agent connects to the app through the command above.

Jump to your client

Claude Desktop Claude Code Cursor VS Code Continue.dev Codex CLI Gemini CLI Zed Warp OpenCode Hermes Agent OpenClaw

Claude Desktop

Anthropic · macOS app

Official docs ↗

Config location

~/Library/Application Support/Claude/claude_desktop_config.json

Snippet

json

{
  "mcpServers": {
    "videoedit": {
      "command": "npx",
      "args": ["-y","@videoedit-mcp/bridge"]
    }
  }
}

Verify

Fully quit (⌘Q) and relaunch Claude Desktop. A tools indicator appears in the bottom-right of the prompt box once VideoEdit is connected.

Gotchas

·Open VideoEdit MCP → Settings → Connect AI Agents to write this config automatically.
·Restart is required — closing the window isn't enough, use ⌘Q.
·Tail logs with `tail -f ~/Library/Logs/Claude/mcp*.log` if it fails to connect.

Claude Code

Anthropic · CLI

Official docs ↗

Config location

Run this command — no config file to edit

Command

shell

claude mcp add --transport stdio --scope user videoedit -- npx -y @videoedit-mcp/bridge

Verify

Inside a Claude Code session, run `/mcp` to see the connected server and its tools. Or `claude mcp list` from the shell.

Gotchas

·The `--` separator before the command is required by Claude Code.
·`--scope user` makes the server available in every project. Use `--scope local` to scope it to the current repo.

Cursor

IDE

Official docs ↗

Config location

~/.cursor/mcp.json (global) or .cursor/mcp.json (project)

Snippet

json

{
  "mcpServers": {
    "videoedit": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y","@videoedit-mcp/bridge"]
    }
  }
}

Verify

Open Cursor settings (⌘⇧J) → Features → Model Context Protocol, toggle the server on, hit refresh. Output panel → MCP Logs shows the connection.

Gotchas

·Open VideoEdit MCP → Settings → Connect AI Agents to write this config automatically.
·The `type: "stdio"` field is required — Cursor uses it to pick the transport.

VS Code

GitHub Copilot · agent mode

Official docs ↗

Config location

.vscode/mcp.json (workspace) or user profile via Command Palette → MCP: Open User Configuration

Snippet

json

{
  "servers": {
    "videoedit": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y","@videoedit-mcp/bridge"]
    }
  }
}

Verify

Open Copilot Chat (⌃⌘I), switch to Agent mode, click Configure Tools. Or run the Command Palette entry `MCP: List Servers`.

Gotchas

·The top-level key is `servers`, not `mcpServers` — VS Code is the odd one out.
·First start shows a trust dialog; skipped when you hand-edit `mcp.json`.

Continue.dev

VS Code / JetBrains extension

Official docs ↗

Config location

.continue/mcpServers/videoedit.yaml

Snippet

yaml

name: VideoEdit MCP
version: 0.0.1
schema: v1
mcpServers:
  - name: videoedit
    type: stdio
    command: npx
    args: ["-y","@videoedit-mcp/bridge"]

Verify

Switch Continue to Agent mode (chat and edit modes ignore MCP). Prompt something that uses a tool — e.g. “list my media library”.

Gotchas

·Agent mode is required — chat/edit modes silently ignore MCP servers.
·The file must have the `name`, `version`, and `schema` top-level fields.

Codex CLI

OpenAI

Official docs ↗

Config location

~/.codex/config.toml

Snippet

toml

[mcp_servers.videoedit]
command = "npx"
args = ["-y","@videoedit-mcp/bridge"]
supports_parallel_tool_calls = true

Verify

Launch `codex`, then issue a prompt that triggers a tool call. Approval prompts confirm the server is wired in.

Gotchas

·TOML, not JSON — Codex is the odd one out.
·Per-tool approval settings live under `[mcp_servers.videoedit.tools.<name>]`.

Gemini CLI

Google

Official docs ↗

Config location

~/.gemini/settings.json

Snippet

json

{
  "mcpServers": {
    "videoedit": {
      "command": "npx",
      "args": ["-y","@videoedit-mcp/bridge"],
      "timeout": 15000,
      "trust": false
    }
  }
}

Verify

Inside a `gemini` session, run `/mcp` for connection status and tool list. CONNECTED = good.

Gotchas

·Known issue: `gemini` does not load `.env` files for MCP servers — any env vars must be in the host shell.

Zed

Editor

Official docs ↗

Config location

~/.config/zed/settings.json

Snippet

json

{
  "context_servers": {
    "videoedit": {
      "command": "npx",
      "args": ["-y","@videoedit-mcp/bridge"]
    }
  }
}

Verify

Open the Zed Agent Panel. A green dot next to the server indicates it's running.

Gotchas

·Zed uses `context_servers`, not `mcpServers` — its own naming.

Warp

Terminal

Official docs ↗

Config location

Settings → AI → MCP Servers → + Add

Snippet

json

{
  "mcpServers": {
    "videoedit": {
      "command": "npx",
      "args": ["-y","@videoedit-mcp/bridge"]
    }
  }
}

Verify

Warp launches and stops the MCP process with the app. The server shows as Running in the MCP Servers list.

OpenCode

SST · terminal coding agent

Official docs ↗

Config location

opencode.jsonc (project root) or ~/.config/opencode/opencode.jsonc (global)

Snippet

json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "videoedit": {
      "type": "local",
      "command": ["npx", "-y", "@videoedit-mcp/bridge"],
      "enabled": true
    }
  }
}

Verify

Inside an opencode session, VideoEdit tools appear in the model's tool list. Prompt something that uses one — e.g. 'list my media library'.

Gotchas

·Unlike most clients, `command` is a single array — arg0 (the executable) goes inside it alongside the args.
·Default tool-loading timeout is 5s. If the server is slow to spawn on first boot, add `"timeout": 15000` to the entry.

Hermes Agent

Nous Research · self-hosted agent

Official docs ↗

Config location

~/.hermes/config.yaml

Snippet

yaml

mcp_servers:
  videoedit:
    command: "npx"
    args: ["-y","@videoedit-mcp/bridge"]

Verify

Restart with `hermes chat`. Hermes registers MCP servers on startup — a successful tool invocation confirms the wiring.

Gotchas

·Top-level key is `mcp_servers` (snake_case), not `mcpServers` — Hermes is the odd one out.
·Config changes require a full Hermes restart. `hermes chat` is the reload.

OpenClaw

Personal AI assistant

Official docs ↗

Config location

~/.openclaw/config.json (or manage via `openclaw mcp` CLI)

Snippet

json

{
  "mcp": {
    "servers": {
      "videoedit": {
        "command": "npx",
        "args": ["-y","@videoedit-mcp/bridge"]
      }
    }
  }
}

Verify

Run `openclaw mcp list` — the `videoedit` entry appears. `openclaw mcp show videoedit` prints the full saved config.

Gotchas

·OpenClaw nests servers two levels deep under `mcp.servers.<name>`, not the flat `mcpServers` most clients use.
·Skip editing the file: `openclaw mcp set videoedit --command 'npx' --args '-y @videoedit-mcp/bridge'`.

Troubleshooting

Common issues

Claude Desktop says the tool isn't available: Fully quit with ⌘Q (not the red close button) and relaunch. macOS keeps the process alive when you just close the window, and the config file is only re-read on a full restart.
The MCP server starts but tool calls fail with auth errors: Open the VideoEdit MCP app and sign in. Your agent connects to the app through the bridge — if you've never signed in, there's no session to use.
"npx: command not found" or the agent can't start the server: npx ships with Node.js. Install the latest LTS from nodejs.org, reopen your terminal, and try again. Most agent hosts already have Node installed.
I want my agent to work on a specific project: Open the VideoEdit MCP app and open the project you want to edit. Your agent then calls the list_projects and switch_project tools — no config changes, no restarts.

Still stuck?

Send us a note with what you tried and we'll get you unblocked.

Contact support