Run via npx

Use npx -y video-context-mcp-server@latest as the command instead of video-context-mcp. No global install required.

Trade-offs:

Adds a short startup delay (npm registry check on each launch)
Always runs the latest published version automatically

VS Code

Update .vscode/mcp.json in your workspace:

{
  "servers": {
    "videoMcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "video-context-mcp-server@latest"],
      "env": {
        "GEMINI_API_KEY": "your-gemini-key",
        "Z_AI_API_KEY": "your-zai-key",
        "DASHSCOPE_API_KEY": "your-dashscope-key",
        "MOONSHOT_API_KEY": "your-moonshot-key",
        "MIMO_API_KEY": "your-mimo-key",
        "DEEPGRAM_API_KEY": "your-deepgram-key",
        "ASSEMBLYAI_API_KEY": "your-assemblyai-key",
        "GROQ_API_KEY": "your-groq-key"
      }
    }
  }
}

Claude Code

claude mcp add \
  --env GEMINI_API_KEY=your-gemini-key \
  --env Z_AI_API_KEY=your-zai-key \
  --env DASHSCOPE_API_KEY=your-dashscope-key \
  --env MOONSHOT_API_KEY=your-moonshot-key \
  --env MIMO_API_KEY=your-mimo-key \
  --env DEEPGRAM_API_KEY=your-deepgram-key \
  --env ASSEMBLYAI_API_KEY=your-assemblyai-key \
  --env GROQ_API_KEY=your-groq-key \
  videoMcp -- npx -y video-context-mcp-server@latest

When to use npx vs global install

	Global install	npx
Startup speed	Fast	Slight delay (registry check)
Auto-updates	Manual (`npm install -g ... @latest`)	Always latest
Disk usage	Persistent	Cached by npm
Best for	Daily use	CI, ephemeral environments

Where to get API keys

See Video Providers and Audio Providers for links to get each API key, free-tier details, and pricing.