# Hippo Video: MCP server status, API access gate and what it does

> Video engagement platform for sales teams to record, automate, and personalize video outreach at scale,... No MCP found, Enterprise leaning. Checked 2026-09-02.

*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) /
[Video Prospecting](../categories/video-prospecting.md) /
Hippo Video

# Hippo Video

[No MCP found](../mcp/none-found.md)
[Enterprise leaning](../gates/enterprise-leaning.md)
[Video Prospecting](../categories/video-prospecting.md)
RESEARCHED
Checked 2026-09-02

> **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1.

Vendor: [hippovideo.io](https://hippovideo.io) · entry id 08-hippo-video · source 08-video-prospecting.md line 90

**What it does**
Video engagement platform for sales teams to record, automate, and personalize video outreach at scale, merging prospect variables into template videos and chaining them into "Video Flows" inside sequences.

**AI features, separated from automation with an AI label on it**
Vendor states an AI Script Generator, an AI Avatar Video Generator, an AI Editor that assembles finished video from a script, a "Humanize AI" layer, and automated name/image/company personalization. None independently verified beyond vendor pricing/product pages.

**RevOps role**
Video-messaging layer plugged into CRM/sequence tools (Outreach, Salesloft, HubSpot, Salesforce); also spans customer-support/CX video beyond pure prospecting.

**MCP server**

- **Status bucket**: No MCP found

- **Auth**: n/a

- **Parsed URLs**: 0 found in the mcp_url field

No server was found at the time of the check. That is a statement about the search, not a promise that none exists. The status was established on 2026-09-02.

mcp_status, verbatim from the file:

none-found

mcp_url, verbatim from the file:

n/a

**Command line**

No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.

**Access gate**

- **Gate bucket**: Enterprise leaning

- **Can a solo operator reach it**: Not without a contract

api_gate, verbatim from the file:

enterprise-leaning (the Video SDK/API has a self-serve 14-day free trial but no published ongoing price - the page routes to talk-to-an-SDK-expert and discuss-pricing-on-call, and the main pricing table never lists API as a tier feature)

**API documentation**

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

**GitHub health**

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

**On GitHub**

The entry carried no github.com URL and the organisation search returned nothing on 2026-09-08. That is a statement about the instrument on that date, not proof the vendor has no GitHub.

**Jobs it can do**

- [Create and send a prospecting video](../jobs/create-and-send-prospecting-video.md)

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.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

**Sources**

- [https://www.hippovideo.io/pricing.html](https://www.hippovideo.io/pricing.html)
- [https://www.hippovideo.io/boost-sales-engagement.html](https://www.hippovideo.io/boost-sales-engagement.html)
- [https://help.hippovideo.io/support/solutions/19000104654](https://help.hippovideo.io/support/solutions/19000104654)
- [https://documenter.getpostman.com/view/5278433/Tz5naxpW](https://documenter.getpostman.com/view/5278433/Tz5naxpW)
- [https://www.hippovideo.io/products/video-sdk/how-video-api-works.html](https://www.hippovideo.io/products/video-sdk/how-video-api-works.html)
- [https://www.hippovideo.io/products/video-sdk.html](https://www.hippovideo.io/products/video-sdk.html)

6 source URLs. Raw sources field, verbatim:

https://www.hippovideo.io/pricing.html, https://www.hippovideo.io/boost-sales-engagement.html, https://help.hippovideo.io/support/solutions/19000104654, https://documenter.getpostman.com/view/5278433/Tz5naxpW, https://www.hippovideo.io/products/video-sdk/how-video-api-works.html, https://www.hippovideo.io/products/video-sdk.html

**Notes, verbatim from the file**
Searches for "Hippo Video MCP" surface only an unrelated product, "Hippo CMMS" (maintenance-management SaaS) - do not confuse the two. Pricing sources disagree on exact figures (Pro ~$20-30/user/mo, Enterprise ~$80/user/mo, 10-seat minimum); treat as approximate. [api_gate 2026-08-25] Reclassified unknown -> enterprise-leaning from the vendor's own page (https://www.hippovideo.io/products/video-sdk.html): the Video SDK/API has a self-serve 14-day free trial but no published ongoing price - the page routes to talk-to-an-SDK-expert and discuss-pricing-on-call, and the main pricing table never lists API as a tier feature. 2026-09-02: re-checked hippovideo.io/llms.txt (404) and web search (hits are Hippo CMMS and Green Hippo media servers, unrelated); no MCP server found.

**Provenance**

- **Entry id**: 08-hippo-video

- **Source file**: 08-video-prospecting.md

- **Source line**: 90

- **Tier**: RESEARCHED

- **last_checked**: 2026-09-02

- **Data baked**: 2026-09-27

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).
