# Viddler MCP server

> Upload and manage private videos, set password protection and custom URLs, and check who watched.

- Listing: https://mcp.tc/i/viddler
- Connect: use the server's own URL `https://mcp.viddler.com/mcp` (with your API key); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: API key
- Category: [Productivity & Projects](https://mcp.tc/c/productivity)
- Vendor: Viddler
- Homepage: <https://viddler.com>
- Docs: <https://viddler.com/for-agents>

## About

Connects an AI assistant to a Viddler account for private video hosting. You can list videos, edit titles and descriptions, upload new files, gate videos behind a password, set custom share URLs and read viewing analytics such as view counts and the viewer log. It also exposes account plan and quota usage, and a tool to send feedback to the Viddler team.

The server is hosted at https://mcp.viddler.com/mcp over streamable HTTP. It needs a Viddler Personal Access Token sent as a Bearer token in the Authorization header. Uploads are two steps: create an upload URL, PUT the file to it, then register the video. Files can be up to 1 GB, and free videos up to 10 minutes.

## What it can do

- List videos and fetch full video records
- Upload videos in two steps and register them
- Update video titles and descriptions
- Protect a video with a password or remove protection
- Set a branded custom URL for sharing
- View counts and viewer log for a video
- Check account plan, quota and video count
- Send feedback or bug reports to Viddler

## Tools (12)

- `viddler_feedback_submit`: Send a feature request, bug report or general feedback to the Viddler team.
- `viddler_access_set_password`: Require a password to play a video, including embeds.
- `viddler_access_remove_password`: Remove password protection so the video plays publicly again.
- `viddler_access_set_custom_url`: Give a video a custom URL slug for sharing.
- `viddler_analytics_get_views`: Get total views, remaining views and the viewer log for a video.
- `viddler_analytics_account_usage`: Return the account's plan, quota used and remaining, and video count.
- `viddler_videos_list`: List videos owned by the authenticated account.
- `viddler_videos_get`: Fetch a video's full record including status, playback id and protection.
- `viddler_videos_set_title`: Update a video's title.
- `viddler_videos_set_description`: Update a video's description.
- `viddler_videos_create_upload`: Start an upload and get a pre-signed upload URL and upload ID.
- `viddler_videos_register`: Create the video record after the file has been uploaded.

## Example prompts

- "List all my Viddler videos"
- "Put a password on video VIDEO\_ID and show me the protection state"
- "Who has watched my onboarding video so far?"
- "How much of my Viddler quota have I used?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http viddler https://mcp.viddler.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
```

2. Replace the placeholder with your key before you run it, then check it with `/mcp` inside Claude Code.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Use the `mcp-remote` bridge, which keeps the key on this computer (a connector added on claude.ai with the key under **Request headers** also shows up here). Open **Settings → Developer → Edit Config** and add:

`claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "viddler": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.viddler.com/mcp",
        "--header",
        "Authorization: Bearer <YOUR_API_KEY>"
      ]
    }
  }
}
```

2. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Viddler&connectorUrl=https%3A%2F%2Fmcp.viddler.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.viddler.com/mcp`. Under **Request headers**, add `Authorization: Bearer <YOUR_API_KEY>` with your key from Viddler, then click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=viddler&config=eyJ1cmwiOiJodHRwczovL21jcC52aWRkbGVyLmNvbS9tY3AiLCJoZWFkZXJzIjp7IkF1dGhvcml6YXRpb24iOiJCZWFyZXIgPFlPVVJfQVBJX0tFWT4ifX0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "viddler": {
      "url": "https://mcp.viddler.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
```

### VS Code

Add it to `.vscode/mcp.json`. VS Code asks for the key the first time and stores it securely:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "viddler": {
      "type": "http",
      "url": "https://mcp.viddler.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "api-key",
      "description": "API key",
      "password": true
    }
  ]
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "viddler": {
      "serverUrl": "https://mcp.viddler.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add viddler --url https://mcp.viddler.com/mcp --bearer-token-env-var VIDDLER_API_KEY
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.viddler]
url = "https://mcp.viddler.com/mcp"
bearer_token_env_var = "VIDDLER_API_KEY"
```

Set `VIDDLER_API_KEY` to your key in the shell that runs Codex.

### Gemini CLI

```bash
gemini mcp add --transport http --header "Authorization: Bearer <YOUR_API_KEY>" viddler https://mcp.viddler.com/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "viddler": {
      "type": "http",
      "url": "https://mcp.viddler.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.viddler.com/mcp`.

## Recent changes

- 2026-10-07 04:20 UTC: Tracking started: 12 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/viddler#history (Atom feed: https://mcp.tc/i/viddler/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.1.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-17 (reachable, asks for credentials)
- Listed: 2026-10-07
- Updated: 2026-10-07

---
Source: https://mcp.tc/i/viddler (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
