Myvideogift

io.github.CryptoLibertusPublished by GitHub account CryptoLibertusv1.0.2Updated Oct 24, 2026

Create and deliver personalized video gifts (photos + an original song) from any agent.

VerifiedSTDIODesktop onlyMedia & Design

Overview

AI-generated overview

Lets an assistant create and deliver personalized video gifts, combining photos with an original song, through the My Video Gift API.

What you can do
This local MCP server connects an assistant to the My Video Gift service so it can create personalized video gifts from photos plus an original song and deliver them. The manifest lists no individual tools, so the exact operations are not documented here. It runs as a local process over stdio and talks to the My Video Gift API.
When to use it
Worth adding when you want an assistant to produce and send personalized video gifts as part of a conversation or workflow, and you already have a My Video Gift account with prepaid credit.
Requirements
Runs locally over stdio, installed from the npm package myvideogift-mcp, so Node.js is needed. Requires a My Video Gift prepaid-credit API key supplied as the MVG_API_KEY environment variable. The optional MVG_API_BASE variable overrides the default API base URL. Network access to the My Video Gift API is required.
Before you install
The server requires the secret MVG_API_KEY, a prepaid-credit key, so usage may consume paid credit. It creates and delivers gifts, which is a write action that sends data to the third-party My Video Gift service. Photos and other content you provide are sent to that service. Keep the key out of shared logs and configuration.

Installation

In SourceWeft

  1. Open Myvideogift in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.