VideoVector MCP Server

Official Model Context Protocol (MCP) server for VectorMethods VideoVector.

This package lets MCP clients such as Claude Desktop, Cursor, Claude Code, and custom agent runtimes search, inspect, and operate VideoVector media intelligence workflows through the public VideoVector API.

Status

• Primary transport: stdio

• Self-hostable transport: Streamable HTTP at /mcp

• Runtime: Node.js 18+

• Package: @vectormethods/videovector-mcp-server

• Command: videovector-mcp

• Server name: videovector

This repository is the public source of truth for VideoVector MCP server code, tool contracts, examples, and release metadata. Private VectorMethods backend deployment wiring, service accounts, project IDs, billing internals, and website source are intentionally not part of this repository.

Related MCP server: Knowledge Server

Install

Use npx from your MCP client:

npx -y @vectormethods/videovector-mcp-server

Or install globally:

npm install -g @vectormethods/videovector-mcp-server

Stdio Usage

VIDEOVECTOR_API_KEY=<your-videovector-api-key> videovector-mcp

Environment variables:

Client Examples

• Claude Desktop: examples/claude-desktop.json

• Cursor: examples/cursor.json

• Generic stdio: examples/custom-stdio.json

• Local Streamable HTTP: examples/streamable-http-local.json

Self-Hosted HTTP

HTTP mode is intended for self-hosted or private network deployments.

npm run build
MCP_TRANSPORT_MODE=http \
VIDEOVECTOR_BASE_URL=https://api.vectormethods.com/api/v2 \
node dist/index.js

Endpoints:

• GET /health

• POST /mcp

• GET /mcp

• DELETE /mcp

HTTP requests must include either:

• Authorization: Bearer <your-videovector-api-key>

• X-API-Key: <your-videovector-api-key>

HTTP hardening variables:

Do not advertise a public hosted remote MCP endpoint until OAuth and MCP protected-resource metadata are enabled for that deployment.

Tools

The server exposes tools for:

• semantic, image, multimodal, and structured metadata search

• index, video, segment, and prompt discovery

• prompt-run estimation, execution, status, results, retries, and cancellation

• prompt management and schema testing

• cloud connectors, import jobs, exports, and webhooks

The machine-readable tool contract is generated at artifacts/tool-contract.json. Private backend and website releases should vendor this artifact for MCP helper endpoints and documentation updates.

Development

npm ci
npm run verify

Useful scripts:

• npm run typecheck

• npm run lint

• npm run build

• npm test

• npm run generate:contract

• npm run check:contract

• npm run check:examples

Use the MCP Inspector for local manual checks:

npx @modelcontextprotocol/inspector

For stdio, point the Inspector to npx -y @vectormethods/videovector-mcp-server and set VIDEOVECTOR_API_KEY.

Security

Never commit API keys, cloud credentials, connector credentials, webhook secrets, service-account JSON, or .env files.

See SECURITY.md for supported versions, disclosure instructions, and operational guidance.