VideoVector MCP Server

io.github.VectorMethodsv2.1.2Updated Oct 8, 2026

Model Context Protocol server for the VectorMethods VideoVector media intelligence API.

VerifiedSTDIODesktop onlyMedia & Design

Overview

AI-generated overview

A local MCP server that connects an assistant to the VectorMethods VideoVector media intelligence API.

What it does
Bridges an assistant to the VectorMethods VideoVector media intelligence API over stdio. The manifest does not list individual tools, so the concrete operations are not documented here. Configuration is limited to the API key, base URL, retry count, and request timeout.
When to use it
Worth considering when you already use the VectorMethods VideoVector media intelligence API and want an assistant to reach it from a local MCP client. Without published tool details, confirm the available operations before relying on it.
Requirements
Runs as a local process on a desktop machine via the npm package @vectormethods/videovector-mcp-server over stdio. Requires the VIDEOVECTOR_API_KEY secret; optional VIDEOVECTOR_BASE_URL, VIDEOVECTOR_MAX_RETRIES, and VIDEOVECTOR_TIMEOUT. Network access to the VectorMethods API is needed.
Before you install
The server requires the VIDEOVECTOR_API_KEY secret, which grants access to your VectorMethods account; store it in the environment rather than in shared files. Requests go to the VectorMethods API, so data sent through the tools leaves your machine. No tools are documented, so review what each call does before use.

Installation

In SourceWeft

  1. Open VideoVector MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v2.1.2LatestOct 8, 2026