VideoDB Director
Official[](https://smithery.ai/server/@video-db/agent-toolkit)
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](https://docs.astral.sh/uv/getting-started/installation)
## 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:
```json
{
"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
```json
{
"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>
```
TDQS
Scored across 4 tools
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 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.
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.
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.