Question 1

What is MCP Media Engine?

Accepted Answer

MCP Media Engine is an async AI media generation API for images, video, and audio. It provides a simple REST API to submit generation jobs, receive webhook callbacks on completion, and retrieve finished media assets. It also ships a first-class Model Context Protocol (MCP) server so AI agents can call image and video generation as native tools.

Question 2

What does "async-first" mean?

Accepted Answer

Every generation job is queued and processed asynchronously. You submit a job, get back a job ID immediately, then either poll for the result or configure a webhook to be notified when it completes. This eliminates HTTP timeouts for long-running AI tasks and makes the API safe to use at any scale.

Question 3

Do I need an account to use MCP Media Engine?

Accepted Answer

Yes. Create a free account at mcpmediaengine.com/dashboard to receive your first API key and complimentary credits. No credit card is required to start.

Question 4

How do I get started?

Accepted Answer

Sign up for a free account, get your API key from the dashboard, then make your first API call. You can also use the MCP server to integrate with Claude Desktop, Cursor, Windsurf, or any MCP-compatible AI assistant. See the Quickstart guide for step-by-step instructions.

Question 5

Is there a free tier?

Accepted Answer

Yes. The Hobby plan is free and includes 100 image generations per month along with 10 video generations. This is perfect for prototyping and personal projects.

Question 6

What types of media can I generate?

Accepted Answer

You can generate still images at various resolutions (512×512 to 1024×1024), short video clips up to 10 seconds at 1080p, and audio using text-to-speech (TTS). More media types and higher resolutions are on the roadmap.

Question 7

Which AI providers does MCP Media Engine support?

Accepted Answer

MCP Media Engine supports multiple AI models. For images: DALL-E 3, Stable Diffusion, Flux 2, and Astria. For video: Stable Video Diffusion and Runway. For audio: text-to-speech (TTS) providers. You can switch providers per-request without changing your integration code.

Question 8

Does MCP Media Engine support DALL-E 3?

Accepted Answer

Yes. DALL-E 3 is fully supported as an image generation provider. You can specify "dall-e-3" as the model parameter when creating an image job. Other available models include "stable-diffusion-xl", "flux-2-turbo", and "astria".

Question 9

Can I use MCP Media Engine with AI agents?

Accepted Answer

Absolutely. MCP Media Engine exposes a Model Context Protocol endpoint, letting agents request, monitor, and retrieve generated media through standard agent tooling. It works with Claude Desktop, Cursor, Windsurf, and any MCP-compatible client.

Question 10

What is batch mode?

Accepted Answer

Batch mode lets you submit hundreds of generation jobs in a single request. Each job is processed in parallel and you receive results via webhook or polling. This is ideal for creating multiple variants, processing content pipelines, or generating assets at scale.

Question 11

How do webhooks work?

Accepted Answer

When creating a job, you can specify a webhook URL. MCP Media Engine will POST to that URL when the job completes (or fails) with the job status and asset URLs. This enables real-time notifications without polling.

Question 12

What is the Model Context Protocol (MCP)?

Accepted Answer

The Model Context Protocol is an open standard that enables AI assistants to connect with external tools and data sources. MCP Media Engine implements the MCP server specification, allowing AI agents to call image and video generation as native tools with standard tool-calling patterns.

Question 13

How does MCP Media Engine handle async generation?

Accepted Answer

MCP Media Engine queues jobs and returns a job ID immediately. You can poll for status or register a webhook to be notified when assets are ready. Long-running jobs never block the request thread.

Question 14

What happens if a job fails?

Accepted Answer

Failed jobs are marked with a failed state and include error details. The API supports configurable auto-retry with exponential backoff. You can also manually retry any failed job via the API or dashboard.

Question 15

Is there rate limiting?

Accepted Answer

Rate limits depend on your plan. Free accounts have lower limits, while paid plans offer higher throughput. Batch mode allows you to queue many jobs efficiently. Contact us for enterprise-level rate limits and dedicated infrastructure.

Question 16

What are the API rate limits?

Accepted Answer

Rate limits vary by plan. Hobby (free) includes 100 image generations/month, Pro ($29/mo) includes 5,000 generations/month, and Enterprise offers unlimited generation with dedicated infrastructure. See the pricing page for details.

Question 17

How long do generated assets stay available?

Accepted Answer

Generated assets are stored and available for retrieval for at least 30 days. Paid plans include extended storage. We recommend downloading assets to your own storage for long-term preservation.

Question 18

How is usage billed?

Accepted Answer

Usage is based on the number of jobs and generation time. Batch jobs are priced per job submitted. See the pricing page for current rates and free tier limits.

Question 19

Do you offer refunds?

Accepted Answer

We offer refunds on unused credits within 30 days of purchase for monthly plans. Annual plans have separate terms. Contact support with your account details to process a refund request.

Question 20

Can I upgrade or downgrade my plan?

Accepted Answer

Yes. You can upgrade or downgrade your plan at any time from the dashboard. Upgrades take effect immediately, and downgrades apply at the start of your next billing cycle.

Question 21

What payment methods do you accept?

Accepted Answer

We accept all major credit cards (Visa, Mastercard, American Express) and PayPal. Enterprise customers can pay via invoice.

Question 22

How is my data handled?

Accepted Answer

Generated assets are stored securely and only accessible via authenticated API calls using your API key. We do not use your inputs for training models. See our Privacy Policy for full details.

Question 23

Is the API secure?

Accepted Answer

Yes. All API calls require authentication with an API key. Traffic is encrypted over HTTPS. We recommend rotating API keys regularly and using environment variables to store sensitive credentials.

Question 24

Do you support SSO or custom authentication?

Accepted Answer

Enterprise plans include SSO support with SAML 2.0. Contact our sales team to discuss custom authentication requirements for your organization.

Question 25

How do I integrate with my application?

Accepted Answer

You can integrate via REST API (JSON over HTTPS), or use the MCP server for agent-native integration. We provide SDKs for Node.js and Python, plus examples for common frameworks. See the docs for detailed integration guides.

Question 26

What SDKs are available?

Accepted Answer

Official SDKs are available for Node.js and Python. The MCP server provides a standard tool interface that works with any MCP-compatible client. Community-maintained SDKs may be available for other languages.

Question 27

Where can I get help?

Accepted Answer

Documentation is available at mcpmediaengine.com/docs. For technical questions, use the support form in your dashboard. Pro and Enterprise customers have access to priority support channels.

Question 28

Can I request new features?

Accepted Answer

Yes. Submit feature requests through the dashboard or contact support. We prioritize features based on customer demand and will update you when requested features are implemented.

Frequently asked questions

//General

//Capabilities & Features

//Technical Questions

//Pricing & Billing

//Security & Privacy

//Integration & Support

Still have questions?