AIVeed

io.github.AIVeed-ioPublished by GitHub account AIVeed-iov0.1.1Updated Nov 8, 2026

Generate AI videos, images and audio (Veo 3.1, Seedance, Kling and more) with AIVeed credits.

The publisher's own server: VEED AI Video Generator

VerifiedSTDIODesktop onlyMedia & DesignAI & ML

Overview

AI-generated overview

AIVeed MCP server lets an assistant generate AI videos, images and audio with hosted models, paid from your own AIVeed credits.

What you can do
  • List the live model catalog with options, accepted inputs and prices, and check your credit balance
  • Start video, image and audio generation jobs and extend a completed Veo 3.1 video by about 7 seconds
  • Poll job status, list past jobs, videos and images, and cancel queued jobs
  • Upload a local image, audio or video file as a generation input, limited to folders you allow
When to use it
Use it when you want an assistant to produce AI video, image or audio assets from a chat client such as Claude, Cursor or VS Code, and you already have an AIVeed account with credits.
Requirements
Node.js 20 or newer, run locally via npx. An AIVeed API key in AIVEED_API_KEY, created in the AIVeed developer console. Network access to the AIVeed API. For local file uploads, the allowed folders must be listed in AIVEED_MCP_UPLOAD_DIRS.
Before you install
Generation tools spend AIVeed credits from your account; failed jobs are refunded and an idempotency key prevents double charges on retries. upload_media is off until you list folders in AIVEED_MCP_UPLOAD_DIRS, and files it uploads get a public URL, so only allow folders with media you are willing to share. Keep client approval prompts on for spending and upload tools.

Installation

In SourceWeft

  1. Open AIVeed 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

aiveed-mcp

MCP server for the AIVeed API: generate AI videos, images and audio (Veo 3.1, Seedance, Kling, Wan, Grok Imagine, GPT Image, Nano Banana and more) from Claude, Cursor, VS Code or any MCP client. Generations are paid in AIVeed credits from your own account.

It talks only to the public REST API at https://api.aiveed.io/v1, with your API key. It holds no other credentials and can do nothing your key could not already do with curl.

Tools

ToolWhat it doesCredits
list_modelsLive model catalog: options, accepted inputs, prices (no key needed)free
get_creditsYour balancefree
generate_video / generate_image / generate_audioStart a job, returns a job idspends
extend_videoAdd ~7 s to a completed Veo 3.1 videospends
get_jobJob status; wait_seconds polls until it finishesfree
list_jobs, list_videos, list_imagesYour jobs and media (permanent URLs)free
cancel_jobCancel a queued job (refunded)free
upload_mediaUpload a local image/audio/video as an input (stdio only)free

Every generate call sends an Idempotency-Key (returned in the result), so a retry with the same key never charges twice. Failed jobs are refunded automatically.

Setup

Create an API key at https://developer.aiveed.io/keys. Node.js 20 or newer is required. Step-by-step setup for each client: https://api.aiveed.io/docs/mcp.

Claude Code

bash
claude mcp add aiveed -e AIVEED_API_KEY=aiv_sk_... -- npx -y aiveed-mcp

Claude Desktop and Cursor (claude_desktop_config.json, ~/.cursor/mcp.json):

json
{  "mcpServers": {    "aiveed": {      "command": "npx",      "args": ["-y", "aiveed-mcp"],      "env": { "AIVEED_API_KEY": "aiv_sk_..." }    }  }}

VS Code (.vscode/mcp.json, or MCP: Add Server in the command palette):

json
{  "servers": {    "aiveed": {      "type": "stdio",      "command": "npx",      "args": ["-y", "aiveed-mcp"],      "env": { "AIVEED_API_KEY": "aiv_sk_..." }    }  }}

Pin a version ([email protected]) if you prefer upgrades to be deliberate.

Local files

upload_media turns a local file into a URL a model can use. That URL is public, so the tool is off until you list the folders it may read in AIVEED_MCP_UPLOAD_DIRS, for example "AIVEED_MCP_UPLOAD_DIRS": "~/Videos/aiveed-inputs". List folders that hold only media you are happy to share; a folder for generation inputs is ideal. Even inside them the tool never reads hidden files or folders, system directories or hard-linked files, and only uploads real image, audio and video files (checked by their content, not just the name).

Generate tools spend credits and upload_media publishes a file, so keep your client's approval prompt on for them rather than auto-approving.

HTTP mode (hosting)

bash
node dist/index.js --http --port 8787 --host 127.0.0.1

Streamable HTTP at POST /mcp, stateless. --host/--port (or AIVEED_MCP_HOST/AIVEED_MCP_PORT) set the address. Every request must carry its caller's own key (Authorization: Bearer aiv_sk_...); AIVEED_API_KEY is ignored, so a hosted instance never spends anyone else's credits. upload_media is not offered (it would read the host's disk).

VariableDefault
AIVEED_MCP_ALLOWED_HOSTSlocalhost,127.0.0.1,[::1]Host header names accepted (a DNS-rebinding guard, not access control); add your public hostname behind a proxy
AIVEED_MCP_ALLOWED_ORIGINSnoneBrowser origins allowed; requests without an Origin header are allowed
AIVEED_API_URLhttps://api.aiveed.ioAPI origin (https only; http allowed for localhost)

Run it behind a TLS-terminating proxy with a rate limit; it binds to 127.0.0.1 by default and answers 503 beyond 64 requests in flight.

Development

bash
npm cinpm test            # vitest; no network, the API is fakednpm run typechecknpm run build       # dist/npm run leak-scan   # credentials, private addresses, personal paths

Work happens on development; main holds released code. See SECURITY.md for the security model and RELEASING.md for how releases are published.

License

MIT

Source: README.md at commit 09f3ce5

Tools

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

Version history

1
  1. v0.1.1LatestNov 8, 2026

Score

50% 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
  • License10 pts

Other Veed integrations