Choose MCP or the API
MCP: connect a compatible AI client to Magic Hour tools or documentation.
API: call Magic Hour directly from your application using HTTPS requests and an API key.
Media-generation MCP
The current hosted media-generation MCP address is:
https://mcp.magichour.ai/
It can create and monitor supported image and video projects, upload image, video, and audio source files, retrieve existing audio projects, and return download links. Speech generation and voice cloning are not available through this media-generation MCP server.
Connect from Claude web or desktop
Open Settings, then Connectors.
Add a custom connector.
Enter
https://mcp.magichour.ai/.Add the connector, then select Connect.
Sign in to Magic Hour if asked, then select Allow on the authorization page.
Verify real API authorization by asking Claude to call
account_retrieve. A returned credit balance confirms the connector can use the Magic Hour API.
Follow the current instructions at magichour.ai/mcp. Treat the API key like a password because MCP requests can spend account credits.
Documentation MCP
Magic Hour also documents https://docs.magichour.ai/mcp for searching API reference material and examples.
Cursor
{ "mcpServers": { "Magic Hour": { "url": "https://docs.magichour.ai/mcp" } }}VS Code
Create .vscode/mcp.json:
{ "servers": { "Magic Hour": { "type": "http", "url": "https://docs.magichour.ai/mcp" } }}Claude Code
claude mcp add --transport http MagicHour https://docs.magichour.ai/mcp
The official pages document the media-generation and documentation addresses separately. Do not assume they are interchangeable. Use mcp.magichour.ai for the hosted media tools and docs.magichour.ai/mcp for documentation lookup.
See the official MCP setup guide.
API setup
Sign in and open /developer.
Create an API key.
Store it in a secret manager or environment variable.
Send it as a Bearer token.
Authorization: Bearer YOUR_MAGIC_HOUR_API_KEY
The production API base address is:
https://api.magichour.ai
Never place a secret key in client-side code, screenshots, public repositories, or support messages.
Current API coverage
Video creation
Documented routes include AI Talking Photo, AI Video Editor, AI Video Translator, Animation, Audio to Video, Auto Subtitle, Character Replace, Face Swap, Image to Video, Lip Sync, Text to Video, and Video to Video.
Image creation and editing
Documented routes include AI Clothes Changer, Face Editor, GIF Generator, Headshot Generator, Image Editor, Image Generator, Image Upscaler, Meme Generator, QR Code Generator, Body Swap, photo Face Swap, Head Swap, Background Remover, and Photo Colorizer.
Audio
Documented routes include AI Voice Generator and AI Voice Cloner.
Project management
The API includes routes to retrieve and delete video, image, and audio projects. Creation requests generally return a project ID. Use the matching project-details route or a configured webhook to follow completion.
See the current API reference overview for exact request fields and endpoint pages.
Uploading files
For API and MCP workflows that need source media:
Request an upload URL.
Upload the image, video, or audio bytes to that URL.
Pass the returned file path to the creation request.
Do not pass raw media bytes as an MCP text argument. Follow the upload tools exposed by the connected server.
Credits and billing
API and media-generation MCP requests use the connected Magic Hour account. Supported API integrations may serve paying end users, subject to the Terms of Service and commercial-use requirements. Keep API keys private; this does not permit sharing account credentials or reselling account access.
Supported creation responses include the project ID and charged credits.
Cost varies by the selected tool and options.
Review current account billing and the endpoint documentation rather than relying on one universal MCP or API price.
Magic Hour does not publish one consolidated universal table for every rate, concurrency limit, upload limit, polling interval, or download-link lifetime. Use endpoint-specific documentation and current account prompts. Do not promise an undocumented limit.
Troubleshooting MCP
Connection fails: confirm the exact server address and that the client supports HTTP MCP connections.
Authorization fails: for Claude connectors, reconnect and complete sign-in and Allow. For API-key clients, create a current key and relaunch the client with its bearer-token configuration. Never paste the key into chat.
Ping works but generation fails: check the tool input, account credits, and returned error.
Upload fails: request a new upload URL and use the returned file path.
Troubleshooting the API
Send support the endpoint, request time, response status, returned message, project ID if available, and a redacted request example. Remove the Authorization header and all secrets first.
Official references
A timeout does not mean the generation stopped
Creation and completion are separate events. If the creation response returned a project ID, retain it and use the matching project-details endpoint or configured webhook to check completion. Download only after the project reports completion and output URLs are available.
If the request timed out before you received an ID, inspect the response and request logs, the relevant account project history, and any configured webhook before repeating the creation request. Blindly repeating a creation request can create a second job and spend more credits. Do not assume every endpoint deduplicates retries. If the outcome is still unknown, contact support with the endpoint, approximate time, redacted request details, and any request or project identifier.
Use the current API reference for exact status values and response fields. Never include your API key in a support message.