# Vidalytics MCP server > Manage Vidalytics videos, player settings, chapters, CTAs and viewer analytics from your AI assistant. - Listing: https://mcp.tc/i/vidalytics - Connect: use the server's own URL `https://api.vidalytics.com/public/v1/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Data & Analytics](https://mcp.tc/c/analytics) - Vendor: Vidalytics - Repository: - Package: npm `@vidalytics/mcp` ## About Connects an AI assistant to a Vidalytics account. You can list and update videos, read stats such as views, play rate, watch time and audience drop-off, edit chapters, captions, tags, CTAs, pause screens and thumbnails, manage folders and settings templates, and upload videos from a URL. Many write tools save changes to the video's draft, and publish\_video makes them live. The server is hosted at https://api.vidalytics.com/public/v1/mcp and uses OAuth sign-in with your Vidalytics account, with read or read+write scope. An npm installer (npx @vidalytics/mcp install) configures Claude, Windsurf and Cursor. ## What it can do - List videos and read video details and embed codes - Read views, play rate, watch time and drop-off stats - Edit chapters, captions and tags as drafts - Create and update CTAs and pause screens - Set or remove video thumbnails - Manage folders and player settings templates - Upload videos from a URL and publish drafts ## Example prompts - "Show views and play rate for my last five Vidalytics videos" - "Where do viewers drop off in my webinar video?" - "Add chapters to my product demo video and publish it" - "Apply my default settings template to the new video" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http vidalytics https://api.vidalytics.com/public/v1/mcp ``` 2. Start Claude Code, type `/mcp`, pick **vidalytics** and choose **Authenticate**. A browser window opens for the Vidalytics sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**. 2. Name it **Vidalytics** and paste this URL: ```url https://api.vidalytics.com/public/v1/mcp ``` 3. Click **Add**, then **Connect**, and sign in when Vidalytics asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://api.vidalytics.com/public/v1/mcp` and click **Add**. 3. Click **Connect** and sign in when Vidalytics asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://api.vidalytics.com/public/v1/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Vidalytics to sign in. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "vidalytics": { "url": "https://api.vidalytics.com/public/v1/mcp" } } } ``` Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"vidalytics","type":"http","url":"https://api.vidalytics.com/public/v1/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "vidalytics": { "type": "http", "url": "https://api.vidalytics.com/public/v1/mcp" } } } ``` VS Code asks you to sign in the first time the server starts. ### 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": { "vidalytics": { "serverUrl": "https://api.vidalytics.com/public/v1/mcp" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add vidalytics --url https://api.vidalytics.com/public/v1/mcp codex mcp login vidalytics ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.vidalytics] url = "https://api.vidalytics.com/public/v1/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http vidalytics https://api.vidalytics.com/public/v1/mcp ``` Then, inside Gemini CLI, run `/mcp auth vidalytics` to sign in. 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": { "vidalytics": { "type": "http", "url": "https://api.vidalytics.com/public/v1/mcp" } } } ``` 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://api.vidalytics.com/public/v1/mcp`. ## Details - Server version: 0.4.1 - Last checked: 2026-10-07 (reachable, asks for credentials) - Listed: 2026-10-07 - Updated: 2026-10-07 --- Source: https://mcp.tc/i/vidalytics (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report