Skip to main content
Glama

To add the MCP server in any config driven MCP Client, following is how the commands and arguments will look like

Install uv

We need to install uv first.

For macOS/Linux:

curl -LsSf https://astral.sh/uv/install.sh | sh

For Windows:

powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

You can also visit the installation steps of uv for more details here

Related MCP server: OpenTool

Run the MCP Server

You can run the MCP server using uvx using the following command

uvx videodb-director-mcp --api-key=VIDEODB_API_KEY

Add the VideoDB Director MCP Server in your favorite Client

Claude Desktop

To configure VideoDB Director MCP server in Claude, you can run the following command

uvx videodb-director-mcp --install=claude

You can manually configure the MCP Server by following these steps:

  1. Open the claude_desktop_config.json file

    In MacOS/Linux:

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

    In Windows:

    code $env:AppData\Claude\claude_desktop_config.json
  2. Add the VideoDB Director MCP Server inside the mcpServers key:

    {
      "mcpServers": {
        "videodb-director": {
          "command": "uvx",
          "args": ["videodb-director-mcp", "--api-key=<VIDEODB-API-KEY>"]
        }
      }
    }

Cursor

To configure VideoDB Director MCP server in Cursor, you can run the following command

uvx videodb-director-mcp --install=cursor

You can manually configure the MCP Server by following these steps:

  1. Inside Cursor, go to Settings > Cursor Settings

  2. Click on MCP

  3. Click on Add new Global MCP Server

  4. Add the VideoDB Director MCP Server under the mcpServers key

    {
      "mcpServers": {
        "videodb-director": {
          "command": "uvx",
          "args": ["videodb-director-mcp", "--api-key=<VIDEODB-API-KEY>"]
        }
      }
    }

Install in Claude and Cursor at the same time.

You can configure VideoDB Director MCP server in Claude and Cursor together, by running the following command

uvx videodb-director-mcp --install=all

Install for Claude Code

claude mcp add videodb-director uvx -- videodb-director-mcp --api-key=<VIDEODB_API_KEY>

Update VideoDB Director MCP package

To ensure you're using the latest version of the MCP server with uvx, start by clearing the cache:

uv cache clean

This command removes any outdated cached packages of videodb-director-mcp, allowing uvx to fetch the most recent version.

If you always want to use the latest version of the MCP server, update your command as follows:

uvx videodb-director-mcp@latest --api-key=<VIDEODB_API_KEY>

Available Tools

4 tools
call_directorC

The Director tool orchestrates specialized agents within the VideoDB server, efficiently handling multimedia and video-related queries. Clients should send queries that Director can interpret clearly, specifying tasks in natural language. Director will then delegate these queries to appropriate agents for optimized results, utilizing defaults and contextual information if explicit parameters are not provided.

Director handles queries such as:

  • Uploading & Downloading:

    • Upload media from URLs or local paths (supported media: video, audio, image)

    • Download the VideoDB generated video streams.

  • Indexing & Search:

    • Index spoken words or scenes in videos (spoken_words, scene indexing; scene indexing supports shot or time-based type)

    • Search VideoDB collections semantically or by keyword (semantic, keyword search; indexing types: spoken_word, scene)

  • Summarization & Subtitles:

    • Summarize video content based on custom prompts

    • Add subtitles in various languages

  • Dubbing:

    • Dub videos into target languages

  • Creating Videos:

    • Generate videos using specific models or engines (Fal, StabilityAI; job types: text_to_video, image_to_video)

    • Compare multiple video generation models (video_generation_comparison)

  • Audio Generation & Editing:

    • Generate speech, sound effects, or background music (engines: ElevenLabs for speech/sound effects, Beatoven for music)

    • Clone voices from audio sources or overlay cloned voices onto videos

    • Censor the video on given prompt

  • Image and Frame Generation:

    • Generate static image frames from videos at specified timestamps

    • Create or enhance images using GenAI models (job types: text_to_image, image_to_image using Fal, Replicate)

  • Video Editing & Clip Generation:

    • Edit or combine multiple videos and audio files

    • Generate targeted video clips from user prompts

  • Streaming & Web Search:

    • Stream videos by video ID or URL

    • Search for relevant online videos (engine: Serp)

  • Transcription:

    • Generate transcripts for videos

  • Pricing & Usage Information:

    • Provide detailed cost information and usage estimates

  • Meeting Recording & Analysis:

    • Record meetings

    • Deploy recording bots to Zoom, Google Meet, or Microsoft Teams

    • Analyze recorded meetings for AI-driven insights

    • Intelligently index and summarize meetings

Clients should provide queries clearly aligned with Director's capabilities, allowing Director to use contextual defaults when explicit parameters like IDs or collection details are not specified.

IMPORTANT: if you have a previous response of this method with an appropriate session_id, please provide that session_id in the next request to continue the conversation. IMPORTANT: It is MANDATORY to send the session_id param if any earlier response from this method exists with a session_id in its output

Inputs: text_message (required), agents, session_id. Returns: object

code_assistantB

Will give you data related to VideoDB SDK which allows developers to use videodb in python. IMPORTANT: Whenever user wants to write code related to videos, youtube videos or VideoDB specifically, always call this tool.

Inputs: no named parameters. Returns: result

doc_assistantC

Context for creating video applications using VideoDB

Inputs: no named parameters. Returns: result

play_videoC

Play the video of the given stream link

Inputs: stream_link (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.4/5.0

    Scored across 4 tools

    Disambiguation1/5

    The tools are highly ambiguous and overlapping. The 'call_director' tool appears to be a monolithic interface that handles nearly all functionality described (uploading, indexing, summarization, dubbing, video creation, audio generation, video editing, streaming, transcription, pricing, meeting analysis, etc.), making it unclear when to use the other tools. 'code_assistant' and 'doc_assistant' might overlap in providing development support, and 'play_video' could be seen as a subset of 'call_director's streaming capability. This creates significant confusion for tool selection.

    Naming Consistency2/5

    Naming is inconsistent with mixed conventions. 'call_director' uses a verb_noun pattern, 'code_assistant' and 'doc_assistant' use noun_noun patterns, and 'play_video' uses verb_noun. While readable, the lack of a uniform pattern (e.g., all verb_noun like 'call_director', 'assist_code', 'assist_docs', 'play_video') reduces predictability. The styles vary without a clear rationale, though they are not chaotic.

    Tool Count2/5

    The tool count of 4 is too few for the broad scope implied by the 'call_director' description, which covers over 20 distinct capabilities (e.g., uploading, indexing, dubbing, video generation). This forces a single tool to handle too many diverse operations, making the surface feel thin and under-scoped. A more appropriate set would break these into multiple specialized tools for better coherence.

    Completeness1/5

    The tool set is severely incomplete relative to the domain described. While 'call_director' lists many video-related operations, the other tools ('code_assistant', 'doc_assistant', 'play_video') do not provide complementary CRUD or lifecycle coverage. For example, there are no dedicated tools for core actions like 'upload_video', 'search_videos', or 'transcribe_video', leaving agents to rely on a single monolithic tool that may not handle all scenarios effectively, leading to potential dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to document data and connect it to AI agents by defining tools and instructions in markdown files. It supports building RAG and text-to-SQL applications that can be deployed as MCP servers, APIs, or CLIs.
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      OpenTool is an MCP server that provides AI agents with secure, authenticated access to a wide range of tools (GitHub, Notion, Slack, etc.) through a single MCP connection. It is fully open-source and self-hostable.
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.
      12 npm
      MIT