
MediaEngine
io.github.Tr1ckyMag1ca1Published by GitHub account Tr1ckyMag1ca1v1.0.3Updated Oct 27, 2026
AI image, video, and audio generation for MCP — one API key, every model, wiring never changes.
Overview
MediaEngine MCP server that lets an assistant generate images, videos and audio from text prompts through one API key and a fixed set of tools.
- What you can do
- Generate images from text prompts, including article hero banners, email headers and social teasers
- Generate videos, including short teasers built from article content
- Generate audio narration and text-to-speech from text
- Track media jobs: check status, wait for completion, and list jobs with filtering and pagination
- Choose quality tiers from basic and standard (Nano Banana) up to premium (GPT-Image)
- When to use it
- Useful when you want an assistant to produce marketing or editorial media — blog hero images, email headers, social graphics, teaser videos or article narration — without wiring each model separately. Also fits workflows that need to poll long-running generation jobs.
- Requirements
- Runs locally over stdio, typically launched with npx from the npm package mcp-media-engine, so Node.js is needed. Requires the MEDIAENGINE_BASE_URL and MEDIAENGINE_API_KEY environment variables; an API key comes from signing up at the provider's site. Optional LOG_LEVEL. Desktop client only.
Installation
In SourceWeft
- Open MediaEngine in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-media-engine
MCP server for MediaEngine — AI-powered image, audio, and video generation for Claude, Cursor, and other MCP clients.
Tools
Installation
Claude Desktop
Add to your claude_desktop_config.json:
Cursor
Add to your .cursor/mcp.json:
Configuration
Quality Tiers
License
MIT
Source: README.md at commit 3a7e6d9
Tools
0Version history
1- v1.0.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts