Skip to content
Viddler logo

Viddler MCP server

Which servers in the official MCP registry are Viddler's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-16

← Back to Viddler

Whose server it is
  • Registry namecom.viddler/viddler-mcpverified in the MCP registry

The registry name sits under viddler.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-16
  • Stateanswerschecked 2026-10-16
  • Tools12
  • Server calls itselfviddler-mcp
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-16 the server answered initialize and tools/list without a sign-in. First answer in 240 ms.

Should an agent connect itNot proven either way yet
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • Signs in by OAuth: the client opens the sign-in on first connect.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-19
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer194 ms
  • Sign-inOAuth: the client signs you in

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers12 tools · read 2026-10-16
  • viddler_feedback_submit

    File a feature request, bug report, or general feedback to the Viddler team from inside your MCP client. Goes into the same triage queue as the in-app feedback widget. Use category 'feature' for feature requests (the default intent)…

  • viddler_access_set_password

    Gate a video behind a secret password. While protected, playback (including embeds) requires the password and Viddler swaps to a Mux signed-playback id. Returns the updated protection state.

  • viddler_access_remove_password

    Turn off password protection for a video. Reverts to the public playback id so the video plays without a password again.

  • viddler_access_set_custom_url

    Give a video a branded, human-friendly custom URL slug for sharing. Returns the updated video.

  • viddler_analytics_get_views

    Return view counts and per-view records for a video: total views, remaining/available views, and the viewer log. The core 'who watched' proof-of-viewing data.

  • viddler_analytics_account_usage

    Return the authenticated account's plan, quota used/remaining, and video count.

  • viddler_videos_list

    List videos owned by the authenticated account.

  • viddler_videos_get

    Fetch the full record for one video: status, playback id, duration, moderation, storage state, protection. Poll this after create_upload until muxPlaybackId is no longer 'pending'.

  • viddler_videos_set_title

    Update a video's title.

  • viddler_videos_set_description

    Update a video's description.

  • viddler_videos_create_upload

    Step 1 of uploading a video. Returns { uploadId, uploadUrl }. PUT the raw video file bytes to uploadUrl (e.g. `curl -X PUT --upload-file video.mp4 '<uploadUrl>'` — no auth header needed, the URL is pre-signed). Then call…

  • viddler_videos_register

    Step 2 of uploading a video: after the file has been PUT to the uploadUrl, call this with the uploadId to create the video record. Returns the video (muxPlaybackId will be 'pending'). Poll viddler_videos_get until muxPlaybackId resolves…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "viddler-mcp": {
      "type": "http",
      "url": "https://mcp.viddler.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http viddler https://mcp.viddler.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.viddler.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.