
Server
Connect your coding agent to Zype so you can manage OTT videos, playlists, analytics, and monetization from the Build phase without leaving the editor.
Overview
com.zype.mcp/server is an MCP server for the Build phase that lets agents manage Zype OTT videos, playlists, analytics, and monetization via the Zype Admin API.
What is this MCP server?
- Remote Streamable HTTP endpoint at mcp.zype.com plus npm package @zype-com/mcp for stdio
- ZYPE_MCP_MODE: readonly, safe (confirmed writes), or full operations
- Covers videos, playlists, analytics, and monetization for OTT services
- Requires ZYPE_API_KEY from the Zype Dashboard
- Open-source server metadata on GitHub (zype/zype-mcp), version 0.5.3
- Server version 0.5.3
- npm package @zype-com/mcp at version 0.5.3
- Three documented access modes: readonly, safe, full
What problem does it solve?
Streaming founders waste build time context-switching between the Zype Dashboard and their repo when playlists, assets, and monetization rules need repetitive updates.
Who is it for?
Indie OTT or media SaaS builders who already use Zype and want agent-driven catalog, playlist, and monetization maintenance during integration work.
Skip if: Teams not on Zype, builders who only need a public marketing site, or anyone who cannot safely store a Zype Admin API key.
What do I get? / Deliverables
After install, your agent can list and mutate Zype resources within your chosen MCP mode so OTT back-office work stays in the same session as your app code.
- Agent-driven Zype video and playlist CRUD within selected mode
- Queryable analytics and monetization configuration changes via MCP tools
- Repeatable OTT back-office workflows scripted from your agent session
Recommended MCP Servers
Journey fit
Video CMS and monetization operations are product construction work—you integrate and automate Zype while building a streaming or media SaaS. Integrations is the canonical shelf for an Admin API–backed MCP that wraps Zype’s HTTP and npm stdio transports.
How it compares
Zype Admin API MCP bridge, not a generic video transcoding skill or a consumer storefront theme.
Common Questions / FAQ
Who is com.zype.mcp/server for?
It is for developers and solo operators running OTT streaming on Zype who want Claude Code, Cursor, or similar agents to manage videos, playlists, analytics, and monetization.
When should I use com.zype.mcp/server?
Use it while building or extending Zype-backed integrations—migrating catalogs, tuning playlists, or scripting monetization—not before you have a Zype account and API key.
How do I add com.zype.mcp/server to my agent?
Register https://mcp.zype.com/mcp for Streamable HTTP or install @zype-com/mcp for stdio, set ZYPE_API_KEY, and optionally ZYPE_MCP_MODE to readonly, safe, or full.