Seedance 2.5 is live on VIDEO AI ME See what it can do

VIDEOAI.ME Get Started

How do I use VIDEO AI ME with any MCP client?

Last updated: September 9, 2026

Any MCP client that speaks streamable HTTP can use VIDEO AI ME: point it at https://videoai.me/api/v1/mcp and send Authorization: Bearer va_live_YOUR_KEY with each request, or let a client that supports OAuth 2.1 discover the sign-in from the server metadata. Create keys at videoai.me/developers on a Pro or Premium plan; the same skills are also available over REST.

How do I connect any MCP client to VIDEO AI ME?

1.Create an API key
Log in at videoai.me and open /developers (Developers in the sidebar). Create a key, optionally with a budget cap in dollars so an agent can never overspend, and copy the full va_live_... value immediately: it is shown exactly once. API keys require an active Pro ($99/month) or Premium ($199/month) subscription.
2.Point the client at the server
Most clients accept a JSON block like the one below; Cursor, Windsurf, Codex-style TOML and YAML configs all map to the same three facts: a url, a streamable HTTP transport, and an Authorization header. Nothing runs locally; the server is hosted.
Generic mcpServers entry
```
{ "mcpServers": { "videoaime": {
  "url": "https://videoai.me/api/v1/mcp",
  "headers": { "Authorization": "Bearer va_live_YOUR_KEY" }
} } }
```
3.Or use OAuth 2.1 discovery
Clients that implement the MCP authorization spec need no key: an unauthenticated request receives a 401 with a WWW-Authenticate challenge pointing at the protected resource metadata below, which names the authorization server, and the client opens the VIDEO AI ME sign-in. Then call list_templates as a first free tool to confirm the connection.
Protected resource metadata (RFC 9728)
```
https://videoai.me/.well-known/oauth-protected-resource/api/v1/mcp
```

What can any MCP client do once connected?

Every skill in the VIDEO AI ME registry: maker skills that generate UGC-style ads, product ads, explainers, and talking-head clips, publishing skills that post and schedule finished videos to your connected social accounts, free discovery skills for templates, actors, voices, and brand memory, and check_run for polling long runs. The full catalog with credit costs and typical durations is on the skill center page, and the REST API equivalent of every tool is described at https://videoai.me/api/v1/openapi.json.

What does access cost?

The API and MCP server are included with the Pro ($99/month) and Premium ($199/month) plans; there is no separate API price. Maker skills spend video credits from the plan's monthly allowance at 1 credit = 1 cent, always quoting the estimate first, and each API key can carry its own budget cap in dollars. Plans and allowances are on the pricing page.

any MCP client setup questions

Direct answers about connecting any MCP client to VIDEO AI ME.

Which transports does the VIDEO AI ME MCP server support?

Streamable HTTP, the current MCP transport, at a single URL with no path suffix. Clients that only launch local stdio servers can bridge it with the mcp-remote package, as the Claude Desktop guide shows, and there is nothing to self-host or keep running on your side.

What does the WWW-Authenticate challenge from VIDEO AI ME contain?

A Bearer challenge whose resource_metadata points at https://videoai.me/.well-known/oauth-protected-resource/api/v1/mcp. That document lists the authorization server and the scopes, so a spec-compliant client can run OAuth 2.1 with PKCE without manual configuration. Clients without OAuth support send a key as a Bearer token instead.

Are the MCP tools and the REST API the same skills?

Yes, one registry feeds both, so a tool name in MCP is the skill id in POST /api/v1/skills/{id}/run and the OpenAPI document at https://videoai.me/api/v1/openapi.json describes the same inputs. Pick MCP for agents that discover tools at runtime and REST for scripts, backends and workflow tools.

Can I build my own agent on top of the VIDEO AI ME MCP server?

Yes. Any MCP-capable framework or SDK can list the tools, read their descriptions with credit ranges, and call them. Respect the two confirmations, the credit quote and the platform list, in your agent loop, and give it a key with a dollar budget cap from videoai.me/developers so a bug cannot drain your allowance.

Why does my MCP client show subscription_required from VIDEO AI ME?

The account behind the key or the OAuth sign-in has no active Pro or Premium subscription, which the MCP server and REST API require. Upgrade at videoai.me/pricing, or check that the key belongs to the subscribed account at videoai.me/developers; the connection works as soon as the subscription is active.