MCP Media Engine_
MCP FOR AGENTS

MCP tools for Claude, Paperclip, and AI agents.

Yes — MCP Media Engine ships a discoverable Model Context Protocol server that Claude, Claude Code, Paperclip, Cursor, Windsurf, Cline, Codex, Gemini CLI, and Goose can call today. Drop one config entry in, and your agent gets async image, video, and audio generation with webhook delivery.

SHORT ANSWER

What is MCP Media Engine, in 60 words?

MCP Media Engine is an MCP server and async API for AI agents. It exposes intent-level tools (hero image, social teaser, email header, teaser video, article narration) and generic generate_image, generate_video, generate_audio tools, plus job lifecycle tools (wait_for_job, get_job_status, list_jobs, cancel_job). Yes — Claude, Claude Code, Paperclip, Cursor, Windsurf, Cline, Codex, and Gemini CLI can call them today over stdio or streamable HTTP at https://mcp.mcpmediaengine.com/mcp.

Get an API keyRead the docsMCP Registry

Listed on the MCP Registry · io.github.tr1ckymag1ca1/mediaengine

discovery

How an agent finds the tool surface.

MCP is a discoverable protocol. When an agent host connects to MCP Media Engine, it issues tools/list over JSON-RPC and receives the full catalog — no hardcoded list in your agent code.

stdio shim

Local agent: npm shim

Claude Desktop, Claude Code, Cursor, Windsurf, Cline, Codex, Goose. The agent host spawns the shim and reads JSON-RPC over stdio.

{
  "mcpServers": {
    "mediaengine": {
      "command": "npx",
      "args": ["-y", "mcp-media-engine"],
      "env": {
        "MEDIAENGINE_API_KEY": "me_live_your_key_here"
      }
    }
  }
}
streamable HTTP

Remote agent: hosted endpoint

Paperclip, Smithery, ChatGPT connectors, and any HTTP-speaking MCP client. Same tool surface, no local process.

POST https://mcp.mcpmediaengine.com/mcp
Authorization: Bearer me_live_...

// JSON-RPC request body
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}
compatible agents

Tested against the agents your team already runs.

The same tool surface — intent-level and generic — works across every MCP-compatible host we tested. Each entry below is a real, supported integration.

Claude Desktop

Native MCP support via claude_desktop_config.json. Add the mediaengine entry, restart, and the tools appear in the tool picker.

Claude Code

SDK support via .claude/claude.md. Spawn the stdio shim from your project and call tools by name from scripts.

Paperclip

Works with the Paperclip agent harness — issue an MCP Media Engine job from any agent routine and receive the asset URL back in the issue thread.

Cursor

AI settings -> MCP Servers. Cursor exposes the tools inside the editor for inline agentic generation.

Windsurf

AI settings -> MCP Servers. Same stdio shim, same tool surface.

Cline

cline_config.json. VS Code extension picks up the mediaengine server on next reload.

Codex CLI

OpenAI agent framework. Launch via npx and pass the API key in env.

Gemini CLI

Google CLI agent. MCP-compatible stdio transport works the same as for Claude.

Goose

Block’s agent framework. Connects to the same stdio shim.

Any MCP client over stdio

Spawn the shim with `npx -y mcp-media-engine` and pass MEDIAENGINE_API_KEY in env. JSON-RPC, no custom protocol.

Direct REST API (no MCP)

POST /api/v1/jobs with Authorization: Bearer me_live_... Useful for non-MCP integrations and legacy clients.

credentials

One API key, two transports.

No OAuth handshake. No per-call refresh. One key, passed either as an env var to the stdio shim or as an Authorization: Bearer header to the hosted endpoint.

  • ✓Format: me_live_... (production) or me_test_... (dev)
  • ✓Issued at https://app.mcpmediaengine.com
  • ✓Per-key rate limiting; read quota with GET /api/v1/tools
  • ✓Optional override: MEDIAENGINE_BASE_URL points the shim at a different host
delivery

Async by design.

Agents submit a job, then either poll or receive a webhook. No long-lived blocking requests in the agent loop. Webhooks are HMAC-SHA256 signed; verify both headers before trusting the payload.

Job lifecycle

queued → processing → done | failed

Batch mode

Up to 500 jobs / request

Signed webhooks

HMAC-SHA256 over ts.body

Two transports

stdio + streamable HTTP

pricing

Start free, scale when the agent does.

Every new account gets a free tier of credits with no credit card. When you outgrow it, paid plans and credit volumes live on the canonical Pricing page — this page does not hardcode numbers so it can never drift from the API.

free tier

25 credits on signup.

Enough for several hero-image generations while you wire MCP Media Engine into your agent. No credit card, no auto-renew.

See full pricing Sign up free
FAQ

Questions agents ask (and the humans wiring them up).

Optimized for AI answer engines — Perplexity, ChatGPT Search, Google AI Overviews — and the developers running them.

Plug MCP Media Engine into your agent today.

25 free credits. No credit card. Works with Claude, Claude Code, Paperclip, and every MCP-compatible host we tested.

Get an API key Read the developer docsMCP Registry

Source: github.com/Tr1ckyMag1ca1/MediaEngine · npm: mcp-media-engine · registry: io.github.Tr1ckyMag1ca1/mediaengine