MakeAIVideo MCP server

The endpoint

https://mcp.makeaivideo.ai

It is a streamable HTTP MCP server. Authentication is required: either OAuth, which most clients handle for you, or an Authorization: Bearer mav_... header.

The older app.makeaivideo.ai/api/mcp address still works and is not going away, so an existing connector does not need changing. New connections should use the address above.

The server is listed in the official MCP Registry as ai.makeaivideo/video-generator, so clients that browse the registry can find it without this page.

Claude and ChatGPT

Both accept a custom connector by URL. Add the server URL above; the client discovers the authorization server, registers itself, and walks you through sign-in. You should not need to paste a key.

• Claude: Settings, Connectors, Add custom connector, paste the URL.
• ChatGPT: Settings, Connectors, add by URL. Availability depends on your plan.

Discovery is served at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server, with dynamic client registration and PKCE (S256). Consent is scoped to read, write and ai, the same three scopes described in Authentication.

Claude Code

Add it with a key:

claude mcp add --transport http makeaivideo \
  https://mcp.makeaivideo.ai \
  --header "Authorization: Bearer $MAV_API_KEY"

Running it locally over stdio

The hosted server above is the easiest route and needs nothing installed. If you would rather run the server yourself, for a client that only speaks stdio or an environment with no outbound HTTP, @makeaivideo/mcp is on npm, with source on GitHub, and exposes the same tools.

MAKEAIVIDEO_API_KEY=mav_... npx -y @makeaivideo/mcp

It authenticates with an API key rather than OAuth, so create one under Developers first. Both routes reach the same API and draw on the same credit balance.

Tools (44)

Renders take minutes. An assistant creates the video, polls get_video_status (respecting poll_after_seconds) and returns the download link. estimate_video_cost quotes the credit cost before anything is spent.

Create videos

create_explainer_video, create_listicle_video, create_story_video, create_ugc_video, create_demo_video, create_article_video, create_spokesperson_video, create_video_from_script

Plan

estimate_video_cost, write_script, structure_text, fetch_article, generate_ideas, enhance_prompt

Track and deliver

get_video_status, list_my_videos, get_download_url, get_captions, create_share_link, export_video

Edit

update_video, generate_video, regenerate_scene, regenerate_voice, cancel_video, delete_video

Characters, voices, music

list_characters, create_character, generate_character_portraits, generate_voice_previews, list_voices, preview_voice, generate_music, list_music, list_templates

Post to social

list_social_accounts, get_connect_link, publish_video, get_publish_status, list_posts

Account and automation

whoami, get_credits, create_webhook, list_webhooks

Posting to social accounts

publish_video posts a finished video to one or more connected accounts, now or at a scheduled time, with one caption or a caption per platform. Supported: TikTok, Instagram (as a Reel), YouTube (a 9:16 video as a Short, 16:9 as a regular video), Facebook (Pages only), LinkedIn, X (videos up to 140 seconds), Threads, Pinterest, Bluesky, Telegram and Discord.

A person connects each account once. get_connect_link returns a short-lived link that you open in a browser to approve access; the assistant cannot complete that step for you. X opens its approval page in a new tab. Bluesky, Telegram and Discord connect in the web app. After that, list_social_accounts returns the account ids, publish_video posts, and get_publish_status returns the link to each live post. The number of connected accounts depends on your plan.

Talking to it directly

For debugging, or a client you are writing yourself. List the tools the server exposes:

curl -X POST https://mcp.makeaivideo.ai \
  -H "Authorization: Bearer $MAV_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

An unauthenticated request returns JSON-RPC error -32001 rather than an HTTP error, which is the usual sign a client dropped the auth header.

MCP server questions

How do I add MakeAIVideo to Claude or ChatGPT?

Paste the server URL, https://mcp.makeaivideo.ai, as a custom connector. The client reads our OAuth discovery documents, registers itself, and walks you through sign-in, so you should not need to paste an API key.

Does the MCP server need an API key?

Not when you connect through OAuth, which is the normal path for Claude and ChatGPT. For a client you are writing yourself, send an Authorization: Bearer mav_... header instead.

What can an assistant do once it is connected?

The same things the API can, subject to the scopes you consent to: read your videos, create and edit them, use the generation helpers, and post finished videos to your connected social accounts. Consent is scoped to read, write and ai.

Can an assistant post videos to TikTok, Instagram or YouTube?

Yes. Once you have connected an account, publish_video posts a finished video, or schedules it, to TikTok, Instagram (as a Reel), YouTube (a 9:16 video as a Short, 16:9 as a regular video), Facebook Pages, LinkedIn, X (videos up to 140 seconds), Threads, Pinterest, Bluesky, Telegram or Discord. A person must connect each account once: get_connect_link returns a link you open in a browser to approve access. X opens its approval page in a new tab.

Why am I getting JSON-RPC error -32001?

The request reached the server without valid credentials. It is returned as a JSON-RPC error rather than an HTTP error, and it usually means the client dropped the Authorization header or the OAuth grant expired.

More MakeAIVideo documentation