Clipy MCP vs Slideshot — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Clipy MCP vs Slideshot
In-depth architectural comparison of the Clipy MCP 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
Clipy MCP
Multimedia Process · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Slideshot
Multimedia Process · Local stdio
Quality: 64/100 (Good) | Auth: No auth required
Verdict Summary: Choose Clipy MCP 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 Clipy MCP when:
You need dedicated capabilities in the Multimedia Process domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
Read your Clipy screen recordings from any agent: search your library, fetch timestamped transcripts, AI summaries, and key moments with video frames (click markers burned in) as inline images. Read-only, free API key. npx -y @clipy/mcp
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
Clipy MCP Tools (21)
search_memory
Search the whole Clipy memory at once** — every screen recording the user made *and* every video they imported — returning the matching moments with timestamps and a URL that opens at that point. Matching is semantic as well as literal, so "login flow" finds a moment where someone said "the authent…
search_recordings
Search your recordings by keyword (title + description).
list_recordings
List your most recent recordings.
get_recording
Metadata for one recording (status, duration, transcript/summary status).
get_transcript
The full timestamped transcript + plaintext.
get_summary
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).
Clipy MCP is categorized under Multimedia Process and uses a local stdio subprocess. In contrast, Slideshot belongs to Multimedia Process using local stdio subprocess. Select Clipy MCP when you need capabilities focused on multimedia process and Slideshot when you require tools for multimedia process.
Privacy-redacted visited routes, console warnings/errors, page exceptions, and failed fetch/XHR metadata. The evidence is explicitly labelled page-reported; headers, bodies, cookies, tokens, typed values, and raw query values are never captured.
wait_for_artifacts
Poll until a recording's transcript/summary finish processing.
download_recording
Download the MP4 locally so you can clip it or extract frames yourself (e.g. with ffmpeg).
get_key_moments
Key moments: timestamps, captions, and click coordinates.
get_agent_context
The full agent-context bundle (summary + key moments + transcript + available browser diagnostics) as markdown.
record
Record a web app headlessly** and upload it as a Clipy recording; returns its share + agent-context URLs. Accepts a `type` (recording kind), `viewports` (sweep several screen sizes into one video), `storageState` / `userDataDir`+`profileDirectory` / `initScript` (record behind a login), and timesta…
+9 more tools listed on main page
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.