VidGuy

io.github.vidguy-aiPublished by GitHub account vidguy-aiv1.2.0Updated Oct 24, 2026

Create short-form videos and images, manage brands, and schedule social content with VidGuy.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowMedia & Design

Overview

AI-generated overview

VidGuy is a remote MCP server that lets an assistant create short-form videos and images, manage brands, and schedule social content.

What you can do
  • Create short-form videos and images
  • Manage brand profiles
  • Schedule social content
  • No tool list is published, so the exact actions available are not documented; the capabilities above come from the provider's description.
When to use it
Useful when you want an assistant to produce short-form video or image content and plan social posts without switching to a separate app. It is a hosted service, so it suits users already working with VidGuy rather than those needing local media processing.
Requirements
A remote endpoint at the provider's site over streamable HTTP. OAuth sign-in is required; no environment variables or headers are declared. A VidGuy account is implied by the OAuth flow.
Before you install
OAuth grants the server access to your VidGuy account, so review the scopes requested. It can create media and schedule social posts, which may publish content publicly or consume paid plan credits; check before letting an assistant act unattended. Content you submit is sent to the provider.

Installation

In SourceWeft

  1. Open VidGuy 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.vidguy-ai%2Fvidguy/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": {
    "vidguy": {
      "type": "http",
      "url": "https://www.vidguy.ai/api/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.2.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.