01
"Create a cinematic image of a crowded Thai night market with a neon Pad Thai sign."
Magic Hour × MCP
Create with Magic Hour from any AI agent
Create images, videos, and audio directly from your prompts in your AI agent.
1
Copy the Magic Hour connector URL
https://mcp.magichour.ai/2
Connect Magic Hour to Claude
In Claude desktop or claude.ai, go to Settings → Connectors, add a custom connector named Magic Hour, and paste the URL.
Open Claude connectors3
Sign in and start
Connect, sign in to Magic Hour and select Allow, then ask Claude to generate an image, video, or audio.
Start creating in Claude01What it can do
Make or edit media from the chat.
The MCP server exposes Magic Hour's current API tools. It also tells the agent how to upload files, wait for renders, and return download links.
01
Image
Generate, edit, colorize, remove backgrounds, and swap faces or heads.
02
Video
Create from text or stills, lip sync, animate portraits, and swap faces.
03
Audio
Generate speech. Use audio files with talking-photo and other tools that accept audio.
02Example requests
Start with a request like one of these.Start with a request like one of these.
Animate a still
02
"Animate this illustrated hooded character with slow camera movement."
03
"Add stylish sunglasses to this photo and keep the result realistic."
03Render jobs
Renders take time.
Your agent can wait.
The first call returns a project ID. A Magic Hour wait tool checks the job and returns the exact signed download URL when the file is ready.
01
Create
Agent calls the matching Magic Hour tool.
02
Wait
Project polls until a terminal state.
03
Upload
Agent uploads source files before the render.
04
Return
Exact download URLs come back.
04Operational details
Details worth knowing.
These answers match the current MCP repo. We leave out anything the code does not confirm.
Model Context Protocol lets an AI assistant call external tools. Magic Hour MCP lets your agent use Magic Hour image, video, and audio tools when you ask for them.
The current MCP repo verifies Claude, Claude Code, and Codex CLI. Cursor is not verified there, so it is not in this setup list.
Yes. With Claude, one is created for you when you sign in to Magic Hour and select Allow. It appears in the Developer Hub, where you can delete it anytime to disconnect. Claude Code and Codex use a key you create there as a bearer token. Never commit or share your key.
Yes. MCP calls the same Magic Hour API. Real generation requests spend Magic Hour credits, and the creation tool reports the charge. Check current pricing before starting a large job.
A render does not finish in the first tool call. The creation tool returns a project ID. A Magic Hour wait tool then checks the job until it completes. If your agent stops after creation, ask it to wait for the Magic Hour result.
For local files, the agent requests an upload URL, uploads the file, then gives the returned file path to a creation tool. The upload tool is called videoAssets_generatePresignedUrl. The name is confusing, but it accepts image, audio, and video files. Finished jobs return signed download URLs. Use each URL exactly as returned.
Restart Claude Code or Codex after adding the server. For Codex, confirm MAGIC_HOUR_API_KEY is available before it starts. If authentication fails, confirm the header uses Authorization: Bearer followed by an active key.
Use the hosted server
Connect Magic Hour MCP.
https://mcp.magichour.ai/Magic Hour MCP. Hosted Streamable HTTP.