VideoDB MCP Server
OfficialAllows importing videos from YouTube by URL to be indexed, searched, and edited within VideoDB.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
VideoDB MCP Server
A remote MCP server that connects Claude (and any MCP client) to VideoDB — upload, index, search, edit, and stream videos straight from a conversation.
Built to meet Anthropic's connector directory review criteria: OAuth 2.1, Streamable HTTP, read/write tool separation, and full tool annotations. Deploys to Vercel in minutes with zero infrastructure — no database, no Redis.
"Upload this YouTube keynote, index it, and find every moment where they demo the product.
Then cut those moments into one highlight reel."Tools
Tool | Kind | What it does |
| read | List collections in the account |
| read | List videos with durations + player links |
| read | Metadata for one video |
| read | Plain or timestamped transcript |
| read | Semantic/keyword search inside one video (spoken or visual index) |
| read | Semantic search across a whole collection |
| read | List visual indexes on a video |
| write | Create a collection |
| write | Upload video/audio/image from a public URL or YouTube |
| write | Transcribe + index speech for search |
| write | Visually index scenes (optionally prompt-steered) |
| write | Cut a clip / supercut from one video → instant stream + player URL |
| write | Stitch moments across videos into one stream (highlight reels) |
| write | Burn subtitles from the transcript |
| write | Default or timestamped thumbnail |
| destructive | Permanently delete a video |
No AI media generation tools are exposed (VideoDB's gen-AI endpoints exist but are excluded — the Anthropic directory does not accept AI image/video/audio generation).
Related MCP server: Video Watcher MCP Server
How auth works (no database)
Claude requires OAuth 2.1; VideoDB accounts use API keys. This server bridges the two with a stateless OAuth layer:
Claude → /oauth/register (Dynamic Client Registration)
→ /oauth/authorize user pastes their VideoDB API key on a consent page
key is verified live against GET api.videodb.io/user
→ /oauth/token PKCE-checked; returns access + refresh tokens
→ /mcp Bearer token per requestEvery artifact (client ID, auth code, access/refresh token) is an AES-256-GCM-sealed payload encrypted with AUTH_SECRET. The user's VideoDB API key travels inside the encrypted token and is decrypted per-request — it is never written to disk, logged, or stored server-side. Tokens are audience-bound to the /mcp URL (RFC 8707), auth codes are PKCE-bound (S256) and live 5 minutes, access tokens 1 hour, refresh tokens 30 days with rotation.
Trade-off to know: with no server-side state, individual tokens can't be revoked before expiry — rotating AUTH_SECRET revokes all connections at once (users just reconnect). If you later need per-user revocation, add a token-ID denylist in Vercel KV.
Deploy to Vercel
Push this repo to GitHub, then Import it at vercel.com/new (or run
npx vercelfrom the repo root — no GitHub needed).Set one environment variable:
AUTH_SECRET— generate withopenssl rand -hex 32.Make sure Fluid compute is enabled (default for new projects) so long-running uploads/indexing fit inside
maxDuration = 300. On Pro you can raise it to 800 inapp/mcp/route.ts.Deploy. Your MCP endpoint is
https://<your-domain>/mcp.
Point a real domain at it (e.g. mcp.videodb.io) before submitting to the directory — the reviewer expects the server domain to match the service.
Connect it to Claude
Claude → Settings → Connectors → Add custom connector (Team/Enterprise: Organization settings → Connectors).
Enter
https://<your-domain>/mcp.Click Connect — the VideoDB consent page opens; paste your API key from console.videodb.io.
Done. Ask Claude to
list my videodb collectionsto smoke-test.
Also works in Claude Code (claude mcp add --transport http videodb https://<your-domain>/mcp) and MCP Inspector.
Local development
npm install
cp .env.example .env # set AUTH_SECRET
npm run dev # http://localhost:3000End-to-end test (no VideoDB account needed)
The e2e suite exercises the full flow exactly like Claude does — discovery, DCR, consent, PKCE, token exchange + rotation, 401 challenges, MCP initialize/tools-list, and tool calls including the async job-polling path — against a mock VideoDB API:
# terminal 1 — mock VideoDB API on :4519
npm run mock
# terminal 2 — the server pointed at the mock
AUTH_SECRET=test-secret-0123456789 VIDEODB_API_BASE=http://127.0.0.1:4519 npm run dev
# terminal 3
npm run e2eAll green = safe to deploy. To test against the real API, just connect from Claude with a real key — every tool maps 1:1 to documented VideoDB endpoints (docs.videodb.io).
Submitting to the Anthropic connector directory
See docs/SUBMISSION.md for the filled-out checklist: portal steps, listing copy, allowed link URIs, test-account requirements, and the compliance acknowledgments.
Project layout
app/mcp/route.ts MCP endpoint (16 tools, annotated) + bearer verification
app/oauth/{authorize,token,register}/ Stateless OAuth 2.1 authorization server
app/.well-known/... RFC 9728 + RFC 8414 discovery metadata
lib/videodb.ts VideoDB REST client (envelope + async-poll protocol)
lib/oauth.ts, lib/crypto.ts Sealed-token machinery
lib/consent-page.ts VideoDB-branded consent screen
scripts/mock-videodb.mjs, scripts/e2e.mjs Full-flow test harnessLicense
Apache-2.0 © Spext Labs Inc. (VideoDB)
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Valmera is the world’s most advanced AI video editor. Edit your recordings in Claude, ChatGPT or another MCP client. Place your own B-roll on a spoken word while the narration continues, correct a caption, trim and reframe. Review the preview and export the approved MP4. Connect with OAuth and an eligible paid Valmera plan.
Kliv is an AI web-app builder. It hosts each app with its own database, edge functions, commerce and email. Connect Claude Code or Cursor to Kliv's MCP server, sign in with your Kliv account, and your AI tool can work on your apps with the same tools the Kliv builder uses. It can edit an app's files, change the database, write and run edge functions, set up products and subscriptions, and run your tests. Then it can build and publish the app. Other MCP clients connect the same way. Your AI tool runs on your own AI subscription, so this work doesn't use your Kliv usage. Kliv still hosts the app and everything behind it. Each person signs in as themselves and reaches only the apps they can edit. The account owner sees every connected tool and can remove one at any time. The address is https://mcp.kliv.dev/mcp for everyone. Sign-in is OAuth in your browser, with your Kliv account. There are no API keys. Setup guide: https://docs.kliv.dev/integrations/mcp
Your YouTube library, in the AI tools you already use: Claude, ChatGPT, Cursor, any MCP client.
VideoDB lets an AI agent watch, search and clip video.
Related MCP Servers
AlicenseNot gradedqualityDmaintenanceEnables video generation from text, images, and more through MCP-compatible apps like Claude and Cursor.55MIT- FlicenseNot gradedqualityDmaintenanceMCP server exposing claude-video functionality for claude.ai web UI via HTTP+SSE, enabling video watching and analysis from claude.ai.-
- FlicenseNot gradedqualityBmaintenanceMCP server for managing video pipelines, integrating media processing (TTS, STT, image generation) and video editing, with a structured plugin system and tunnel to Claude AI Web.-
- AlicenseNot gradedqualityDmaintenanceOne connector for the whole MCP catalog — 15,000+ servers plus your team's private MCPs — callable from Claude, ChatGPT, Cursor and VS Code through a single OAuth endpoint. No per-server install.MIT