Mediamcp vs Slideshot — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mediamcp vs Slideshot
In-depth architectural comparison of the Mediamcp and Slideshot MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Mediamcp
Multimedia Process · Local stdio
Quality: 64/100 (Good) | Auth: API Key required
Slideshot
Multimedia Process · Local stdio
Quality: 64/100 (Good) | Auth: No auth required
Verdict Summary: Choose Mediamcp if you need specialized Multimedia Process tools running via a local process. Choose Slideshot if your workspace requires Multimedia Process integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Mediamcp when:
You need dedicated capabilities in the Multimedia Process domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: OPENROUTER_API_KEY, MEDIAMCP_API_KEY, MEDIAMCP_BASE_URL, MEDIAMCP_MODEL, MEDIAMCP_VIDEO_MODEL.
Image generation and editing plus video generation (Veo, Sora, Seedance) via OpenRouter or any OpenAI-compatible API. Saves files to disk with token-cheap inline previews, resumable video jobs, live model listing, and a config-diagnostics tool. npx -y mediamcp.
Convert HTML to PDF/PNG/WebP/PPTX slide carousels with 11 themes (LinkedIn, Instagram, pitch decks, infographics). Pixel-perfect Puppeteer rendering, dimension-aware reflow for portrait/landscape, token-efficient JSON mode. npx slideshot-mcp.
Category & Scope
Tools & Capabilities Breakdown
Mediamcp Tools (6)
generate_image
Generate one or more images from a text prompt using a cloud AI model. Every image is saved to disk and its absolute path is returned, along with a small inline preview. Use edit_image instead when starting from an existing image.
edit_image
Edit or transform existing image(s) with a text instruction — restyle, add or remove elements, change background, or combine several images into one scene. The result is saved to disk and its absolute path is returned, along with a small inline preview.
generate_video
Generate a video from a text prompt, and optionally from an input image (image-to-video). Async job: starts generation, then waits and polls. Video generation typically takes 1-5 minutes. The finished file is saved to disk and its absolute path is returned. If waiting times out, a polling_url is returned — pass it to check_video_status later instead of starting a new (billed) job. For image-to-video, pass first_frame_image so the clip animates from that exact picture (e.g. a still produced by generate_image). Image inputs require an image-to-video-capable model such as 'bytedance/seedance-2.0', 'bytedance/seedance-2.0-fast', or 'google/veo-3.1'.
check_video_status
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Mediamcp is categorized under Multimedia Process and uses a local stdio subprocess. In contrast, Slideshot belongs to Multimedia Process using local stdio subprocess. Select Mediamcp when you need capabilities focused on multimedia process and Slideshot when you require tools for multimedia process.
Check a previously started video generation job (from generate_video's polling_url or video id). If the job has completed, downloads the video, saves it to disk, and returns the absolute path.
list_models
List image- and video-capable model slugs available on the configured endpoint, with pricing where known. Use this to pick a `model` value for generate_image, edit_image, or generate_video.
check_config
Diagnose the mediamcp server setup: endpoint, API key presence and validity, default models, and output directory writability. Run this first when any other mediamcp tool fails.
Slideshot Tools (6)
discover_themes
MANDATORY first step — all other tools REJECT until this is called. Returns themes, orientation presets, token-usage modes, and output formats. Use ONLY the native selector prompts from the "ask" array — DO NOT render themes as a separate markdown list. DO NOT ask how many slides (you decide based on topic). After user picks options, show a data outline of proposed slides and WAIT for confirmation before calling create_slides.
create_slides
Create slides. IMPORTANT: Use mode=default unless the user explicitly chose token_saver. mode=default = AI writes full HTML (best quality). mode=token_saver = AI sends JSON, server uses basic templates. REQUIRES discover_themes first AND user must have confirmed the data outline. After this tool saves the HTML, you MUST show the htmlPath as a code preview artifact. Then STOP and ask the user to confirm. DO NOT call render_slides until the user explicitly confirms.
render_slides
Final render to PDF/WebP/PNG/PPTX. Accepts html string OR htmlPath. Supports width, height, selector, scale, webpQuality, orientation, pptxMode, pptxFilename, slideRange. NEVER call render_slides in the same turn as create_slides. When the user provides an existing HTML file path, pass it as htmlPath and call this tool directly — no discover_themes or create_slides needed. For the full slide-creation workflow, REQUIRES both discover_themes AND create_slides first, and ONLY call AFTER user confirms the preview. Returns file paths on disk.
list_themes
Idempotent read-only listing of all available themes (8+). Unlike discover_themes, this does NOT start a slide-creation workflow — call it any time the user asks "what themes are there?" mid-conversation. Returns the same tiered theme catalog (primary/secondary). Models MUST present every theme returned, never truncate.
edit_slides
Token-efficient partial edits on a previously-generated HTML deck. Use this INSTEAD of regenerating the whole deck for small changes — it saves 60-90% tokens vs a full rewrite. Operations: replace_slide (swap one slide block by 1-indexed slideIndex), patch_css (append CSS rules to <style>), swap_token (replace a CSS variable's value, e.g. {"--coral": "#FF0000"}), patch_class (add/remove a class on a specific slide, e.g. {"add": "dark"}). Reads from cache or htmlPath; saves the updated HTML and returns the new htmlPath. After editing, show the htmlPath as a preview artifact and STOP — do NOT call render_slides until the user confirms.
health_check
Verify Puppeteer/Chromium can launch. Use when render fails.