VEED
MCP server by VEED
Generate AI talking-head videos from text with custom characters and voices, straight from your assistant.
Connect to VEED
VEED needs sign-in. Connect with its own URL:
Your client opens VEED’s sign-in the first time you use it. The token stays between your client and VEED.
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/veedAbout
VEED Fabric lets an AI assistant create talking-head videos with AI avatars. You choose from 24+ characters and voices in several languages and accents, pick landscape, portrait or square output, and follow generation progress. It can also show credit balance and cost estimates before generating, and organize videos across workspaces.
It runs as a hosted streamable HTTP endpoint at https://www.veed.io/api/v1/mcp. You sign in with a VEED account through OAuth. Generation uses AI Playground credits, which are included with paid plans or can be purchased. Generated videos are stored in your VEED workspace.
What you can do
- Generate talking-head videos from text with AI avatars
- Browse 24+ characters and multi-language voices
- Choose landscape, portrait or square aspect ratios
- Track generation progress
- Check credit balance and cost estimates before generating
- Manage videos across multiple workspaces
Tools
VEED lists its tools only after you sign in, so we can’t show them here. Your client lists them once you’re connected.
Example prompts
Create a 30 second talking-head video introducing our new product.
Show me the available avatar characters and voices.
How many VEED credits do I have left?
Make a portrait video of a presenter explaining our weekly update.
Set up
Every client connects to veed.io, and VEED asks you to sign in the first time. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http veed https://www.veed.io/api/v1/mcp- Start Claude Code, type
/mcp, pick veed and choose Authenticate. A browser window opens for the VEED sign-in.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Settings → Connectors and click Add custom connector.
- Name it VEED and paste this URL:
https://www.veed.io/api/v1/mcp- Click Add, then Connect, and sign in when VEED asks.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://www.veed.io/api/v1/mcpand click Add. - Click Connect and sign in when VEED asks.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, open Settings → Security and login and turn on Developer mode.
- Go to
chatgpt.com/pluginsand click + to create an app for a remote MCP server. - Paste
https://www.veed.io/api/v1/mcpas the server URL and choose OAuth. ChatGPT sends you to VEED to sign in.
Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"veed": {
"url": "https://www.veed.io/api/v1/mcp"
}
}
}Cursor shows Needs login next to the server. Click it to sign in.
VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"veed","type":"http","url":"https://www.veed.io/api/v1/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"veed": {
"type": "http",
"url": "https://www.veed.io/api/v1/mcp"
}
}
}VS Code asks you to sign in the first time the server starts.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"veed": {
"serverUrl": "https://www.veed.io/api/v1/mcp"
}
}
}- Refresh the MCP server list in Cascade and sign in when asked.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add veed --url https://www.veed.io/api/v1/mcp
codex mcp login veedOr edit ~/.codex/config.toml directly:
[mcp_servers.veed]
url = "https://www.veed.io/api/v1/mcp"Gemini CLI
gemini mcp add --transport http veed https://www.veed.io/api/v1/mcpThen, inside Gemini CLI, run /mcp auth veed to sign in.
This adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"veed": {
"type": "http",
"url": "https://www.veed.io/api/v1/mcp"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://www.veed.io/api/v1/mcp.
FAQ
Can I paste mcp.tc/i/veed into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://www.veed.io/api/v1/mcp, so your client talks to VEED directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.
Does VEED need an API key or a sign-in?
Yes, you need a VEED account. The first time your client connects, it opens VEED’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.
Is VEED a remote or a local server?
Remote. VEED hosts it at https://www.veed.io/api/v1/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can VEED do?
You can generate talking-head videos from text with AI avatars, browse 24+ characters and multi-language voices and choose landscape, portrait or square aspect ratios.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Who wrote this page?
mcp.tc’s robot read VEED’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
Embed
Show VEED in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
README badge
[](https://mcp.tc/i/veed)<a href="https://mcp.tc/i/veed"><img src="https://mcp.tc/i/veed/badge.svg" alt="VEED on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/veed.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/veed" title="VEED on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/veed.jsonmcp.tc isn’t affiliated with VEED. This page was built from VEED’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.