Vivu

io.github.vivuaiPublished by GitHub account vivuaiv1.0.0Updated Oct 24, 2026

Search your video library with natural language and retrieve relevant moments through MCP.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Vivu is a remote MCP server that lets an assistant search a video library in natural language and pull out relevant moments.

What you can do
  • Search a video library using natural-language queries
  • Retrieve the relevant moments that match a query
  • No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Useful when you keep video content in Vivu and want an assistant to find specific moments in it by describing what you are looking for, instead of scrubbing through footage manually.
Requirements
A remote MCP endpoint at mcp.vivu.ai connected over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
Access is tied to an OAuth account, so the assistant can reach whatever video library that account can see; review the scopes granted during sign-in. The published material does not describe write, delete or sharing behavior, so confirm what the tools can change before use.

Installation

In SourceWeft

  1. Open Vivu 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/io.github.vivuai%2Fvivu/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": {
    "vivu": {
      "type": "http",
      "url": "https://mcp.vivu.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.