home / mcp / vimeo mcp server

Vimeo MCP Server

MCP Server generated by mcp.ag2.ai

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "ag2-mcp-servers-vimeo": {
      "command": "python",
      "args": [
        "mcp_server/main.py",
        "stdio"
      ],
      "env": {
        "CONFIG": "{...}",
        "SECURITY": "YOUR_API_KEY_OR_TOKEN",
        "CONFIG_PATH": "path/to/mcp_config.json"
      }
    }
  }
}

This MCP Server runs a Model Context Protocol service for Vimeo’s OpenAPI-based API, allowing clients to interact with Vimeo data through context-aware requests. It exposes a standard MCP interface that can be consumed by MCP clients to fetch, reason about, and act on Vimeo API models in a consistent, scalable way.

How to use

You start the MCP Server in stdio mode and then connect your MCP client to it. The server reads its configuration from environment variables or a JSON file and exposes a transport layer you can use to send requests and receive responses. Use the server to query the Vimeo OpenAPI-based model context and perform actions that align with the MCP protocol.

How to install

Prerequisites ensure your environment can run Python 3.9 or newer and has pip and uv available.

Step 1: Clone the project directory.

git clone <repository-url>
cd mcp_server

Step 2: Install development dependencies. You can install them via pip or with uv if you prefer an editable setup.

pip install -e ".[dev]"

Alternatively, install in editable mode using uv.

uv pip install --editable ".[dev]"

Running the Server

You launch the MCP Server using the main script in stdio mode. This starts the server in a way that allows you to interact with it via standard input/output streams, which is convenient for development and testing.

python mcp_server/main.py stdio

Configuration and environment

Configure the server using environment variables. You can point the server at a JSON configuration file or provide the configuration as a JSON string.

Environment variables shown for the server:

- CONFIG_PATH: Path to a JSON configuration file (for example, mcp_server/mcp_config.json). - CONFIG: A JSON string containing the configuration. - SECURITY: Environment variables for security parameters (such as API keys or tokens).

Building and publishing

The project uses Hatch for building and publishing. Build and publish commands are available to package and share the MCP server.

hatch build
```
```
hatch publish

Notes and tips

If you need to test interactions, you can start the server in stdio mode and then drive it from your MCP client. Ensure you provide the proper configuration via CONFIG_PATH or CONFIG and any required security credentials via SECURITY.