Zype

com.zype.mcpPublished by mcp.zype.comOfficial publisherv0.5.3Updated Oct 24, 2026

Manage videos, playlists, analytics, and monetization for OTT streaming services.

VerifiedStreamable HTTPWeb executableData & AnalyticsMedia & Design

Overview

AI-generated overview

Zype's MCP server lets an assistant manage an OTT streaming service: videos, playlists, analytics and monetization, via a hosted endpoint or a local npm process

What you can do
Manage videos and playlists for an OTT streaming service, including organizing content into collections and playlists. Review analytics for the streaming service. Handle monetization settings for the service. Access is governed by a mode setting: read-only, safe (writes allowed, destructive actions need confirmation), or full.
When to use it
Useful when you run an OTT or video streaming service on Zype and want an assistant to help with content organization, playlist management, analytics review or monetization tasks without switching to the Zype dashboard.
Requirements
A Zype account with an Admin API key, supplied as ZYPE_API_KEY. Connect either to the hosted endpoint at mcp.zype.com with OAuth, or run the npm package locally over stdio. The ZYPE_MCP_MODE variable sets the access level (readonly, safe or full).
Before you install
The server can write and, in full mode, perform destructive operations on your Zype account, so start in readonly or safe mode. The Admin API key is a sensitive credential granting broad account access; keep it out of shared configuration. Review what the assistant changes before relying on it.

Installation

In SourceWeft

  1. Open Zype in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.zype.mcp%2Fserver/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.5.3LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.