# Vidyard: products, MCP servers and connect URLs, one vendor page > Vidyard (vidyard.com): 1 product in The GTM MCP Directory, 0 with an official MCP server, 0 answering a live handshake, 0 tools catalogued. Data baked 2026-09-27. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* *Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.* --- [Directory](../index.md) / [Vendors](../vendors/index.md) / Vidyard # Vidyard 1 product in the directory 0 official MCP servers 0 live handshakes Data baked 2026-09-27 Vendor domain: [vidyard.com](https://vidyard.com) · vendor page id vidyard-com **The rollup** - **Products**: 1, facts checked by hand 2026-08-24 - **Official MCP servers**: 0 of 1, as recorded on 2026-08-24 - **Community MCP servers**: 1 of 1 - **Live handshake**: 0 of 1 answered an MCP initialize, 1 probed, 2026-09-04 - **Repo local**: 0 of 1: a server you install and run yourself - **Docs only**: 1 of 1: the recorded URL is a page about the server, not the server - **Tools catalogued**: not measured on any product of this vendor - **Bench tested**: 0 of 1 here, 1 of 1,252 across the directory - **Ships a CLI**: 1 of 1 official, 0 community only, 0 none found, harvested 2026-09-27 - **GitHub organisation**: [github.com/Vidyard](https://github.com/Vidyard), tied to the domain with evidence 2026-09-08 A live handshake means the URL answered an MCP initialize as a server on the probe date. It is liveness and nothing more: nobody has run its tools. A tool being catalogued means a server names it, by answering tools/list, in its own source, or in the vendor's documentation. None of them has been called. A tool count of 0 means not measured, never zero tools. **Products, 1** ### [Vidyard](../tools/vidyard.md) AI-powered video-selling platform for recording, personalizing (including AI-avatar-generated), and sending trackable video messages to prospects via email, CRM, and sales-engagement sequences. [Community MCP](../mcp/community.md) · [Paid, self-serve](../gates/paid.md) [Video Prospecting](../categories/video-prospecting.md) RESEARCHED - **Endpoint probe**: docs page, not an endpoint, 2026-09-04 - **Connect URL**: [https://viasocket.com/mcp/vidyard](https://viasocket.com/mcp/vidyard) (docs page) - **Tools catalogued**: not measured - **last_checked**: 2026-08-24 **The gates, in plain words** 1 of 1 paid and self serve, API access by paying, no sales call. The gate is the api_gate field on each product entry, established by hand on the last_checked date shown above. It records whether a solo operator can get API access without a contract. Money is not tracked. **Jobs the vendor says its products do** - [Create and send a prospecting video](../jobs/create-and-send-prospecting-video.md) - [Read outreach performance](../jobs/read-outreach-performance.md) 2 distinct job labels, the union across 1 product, tagged 2026-08-25. A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records. **Connect URLs** - [https://viasocket.com/mcp/vidyard](https://viasocket.com/mcp/vidyard) (Vidyard, docs page, probed 2026-09-04) An endpoint is where an agent connects. A docs page is where a person reads about connecting. Both are published because both are what the probe found; an agent needs the first. **Command line** ### [Vidyard](../tools/vidyard.md) vy-cli official CLI ``` npm install -g @vidyard/vy-cli ``` quoted from [https://www.npmjs.com/package/@vidyard/vy-cli](https://www.npmjs.com/package/@vidyard/vy-cli) on 2026-09-27, via npm harvested 2026-09-27, all on the [tool page](../tools/vidyard.md). A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. **On GitHub** [github.com/Vidyard](https://github.com/Vidyard) tied to the vendor by rule 3, account website www.vidyard.com has the vendor's domain, confidence strong - **Public repositories**: 4, forks excluded, as read on 2026-09-08 - **Mention MCP**: 0 of them - **Look like CLIs**: 0 of them - **Latest push**: 2026-05-11 The five most recently pushed, on 2026-09-08: | Repository | Kind | Description | Stars | Pushed | Latest release | |---|---|---|---|---|---| | [DesktopAppReleases](https://github.com/Vidyard/DesktopAppReleases) | app | To house official releases of the Vidyard Desktop App | 0 | 2026-05-11 | 2.3.5 | | [.github](https://github.com/Vidyard/.github) | other | Public org repo | 0 | 2026-02-03 | | | [wordpress-plugin](https://github.com/Vidyard/wordpress-plugin) | plugin or integration | | 2 | 2019-09-30 | | | [dsm](https://github.com/Vidyard/dsm) | other | Online MySQL data migrations gem | 2 | 2017-04-18 | | Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08. **What this page does not claim** A job tag is a vendor claim: it means the vendor says the product does this, and it is not a test result. A listed tool has not been run: the catalogue says what an agent could try, not what works. 1 of 1,252 directory entries are bench tested, meaning somebody personally ran the tool on a stated date, and 0 of this vendor's 1 product are among them. There is no verdict here on whether this vendor is better than another. Vendor pages group the directory's canonical product entries by vendor_domain. The vendor name is the product display name that matches the domain when several products share it; nothing on this page is typed by hand. Data baked 2026-09-27 by build_directory.py (phase 1).