Veevid AI

ai.veevidPublished by veevid.aiOfficial publisherv1.0.1Updated Oct 26, 2026

Generate AI videos, images and audio on Veevid with Kling 4.0, Seedance 2.5, Veo 3.1 and more.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant generate AI videos, images and audio on Veevid using models such as Kling 4.0, Seedance 2.5 and Veo 3.1.

What you can do
  • Generate AI video from prompts using hosted models such as Kling 4.0, Seedance 2.5 and Veo 3.1
  • Create AI images and audio through the same Veevid platform
  • Work with the Veevid generation service directly from a connected assistant over a remote endpoint
  • The manifest lists no individual tools, so exact operations are not documented here
When to use it
Useful when you want an assistant to produce AI-generated video, image or audio assets on Veevid without leaving the chat, and you already have or plan to get a Veevid API key.
Requirements
A remote streamable HTTP endpoint at veevid.ai; no local package or runtime needed. A Veevid account and API key are required, sent as a bearer token in the Authorization header. Network access to veevid.ai.
Before you install
The server requires a Veevid API key in the Authorization header; keep it private and scope it as narrowly as the service allows. Generation on a hosted platform may consume paid credits or quota, so check Veevid's pricing before heavy use. Prompts and generated assets are sent to Veevid as a third party.

Installation

In SourceWeft

  1. Open Veevid AI in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/ai.veevid%2Fveevid/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.

{
  "mcpServers": {
    "veevid-ai": {
      "type": "http",
      "url": "https://veevid.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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

2
  1. v1.0.1LatestOct 26, 2026
  2. v1.0.0Oct 18, 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.