Generate images, video, and audio for AI-agent workflows.
MCP Media Engine is an async API that lets agents like Claude generate hero images, illustrations, video clips, and voiceovers — without leaving your stack. Queue a job, get an asset URL back.
mcpmedia $ create image --model flux-2-turbo --prompt "hero image for blog post about AI agents" --webhook https://app.com/hooks/media job_7f91c2 queued status: processing eta: 00:12 [████████████░░░░] 85% asset_url: pending_
Image generation
Product shots, hero images, and thumbnails at scale.
Video generation
Short-form clips from text prompts.
Audio generation
Speech, voiceover, and sound assets.
Webhook delivery
Get notified when assets are ready.
Batch processing
Submit hundreds of jobs at once.
One API for every media type.
Images, video, audio, and batch jobs — all behind a single async interface. Your agent submits a job, the queue handles the rest.
Image Mode
Generate hero images for blog posts, product shots, thumbnails, and creative assets. Supports multiple models including Flux 2 Turbo.
Video Mode
Run short-form video generation jobs without blocking the user session. Async queue handles long render times.
Audio Mode
Create speech, voiceover, and audio assets from backend workflows. Ideal for narration on AI-generated content.
Batch Mode
Submit hundreds of generation jobs in one request, track every state, and retrieve assets as they complete.
Webhook Delivery
Receive status changes and completed asset URLs directly in your application. No polling required.
Agent Mode (MCP)
AI agents request, monitor, and retrieve generated media using the Model Context Protocol (MCP). Works with Claude, Cursor, and other MCP-compatible tools.
From prompt to asset URL in four steps.
Submit a generation job, the queue processes it asynchronously, and you receive the finished asset through polling or webhooks.
PROMPT
You send a prompt and parameters.
mcpmedia $ create img --prompt "product"
QUEUED
The job is validated and queued.
job_01 [ ] job_02 [ ] job_03 [ ] job_04 [ ]
PROCESSING
The rendering engine generates your media.
rendering [### ] 58% 00:18
RENDERED
The asset is finalized and stored.
.-"""-. / _ _ \ | (o o) | | \_/ | \ ___ / '.___.'
DELIVERED
You receive asset URLs through API or webhook.
200 OK asset_url > webhook ok done.
Built for backend workflows.
Submit jobs from your server, agent, or workflow runner, then retrieve assets when they are ready.
/v1/jobscurl -X POST https://api.mcpmediaengine.com/v1/jobs \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"type": "image",
"model": "stable-diffusion",
"prompt": "editorial product photo",
"webhook_url": "https://app.com/hooks/media"
}'Built for production media workflows.
From hero images on agent-written blog posts to batch product imagery — real media jobs, not toy demos.
Async by default.
Long-running media jobs belong in a queue, not on the request thread.
Queue
Long-running jobs stay off the request thread.
Status
Track every generation from queued to complete.
Webhooks
Notify your app when assets are ready.
Retries
Recover failed jobs with clear retry behavior.
Storage
Retrieve final media through stable asset URLs.
Common questions.
Technical details about the async media generation API and MCP integration.
Add media generation to your agent workflow.
25 free credits. No credit card required.