F
licenseC
qualityB
maintenanceProvides a durable MCP media pipeline for image, video, audio, and storyboard generation, with FFmpeg composition, provider routing, and resumable long-running jobs.
21
-
Dreep MCP Server
Related Servers
Alternatives to Dreep MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables applications and AI agents to inspect, convert, extract, and process media through asynchronous HTTP and MCP tasks, with optional natural-language planning and A2A interoperability.MIT
- AlicenseNot gradedqualityAmaintenanceEnables document conversion and processing through MCP, including Office/PDF/Markdown conversions, OCR, and PDF operations like split, rotate, encrypt, and extract.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to inspect, convert, resize, compress, crop, rotate, watermark, background-remove, and batch-process images with secure path confinement and result verification.14MIT
- AlicenseNot gradedqualityBmaintenanceEnables image and video generation and editing through MCP tools, including image editing, upscaling, background removal, video generation, image-to-video, and video extension. Video generation runs asynchronously with job status and result retrieval.MIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to analyze, inspect, and manipulate images and videos with deterministic FFmpeg/sharp tools and pluggable AI providers, returning timestamped, evidence-backed results that can be independently re-verified.1-
TDQS
A3.8/5.0
Scored across 14 tools
Disambiguation4/5
Most tools have clearly distinct purposes tied to a resource+action: upload, transform URL building, listing, image/doc operations, folder and preset management. The only friction is the upload trio (upload_file, create_upload_url, confirm_upload), where an agent must understand that create_upload_url handles large/unreadable files and confirm_upload finalizes them, but the descriptions do spell this out.
Naming Consistency5/5
Every tool follows a consistent verb_noun pattern: upload_file, confirm_upload, build_delivery_url, create_upload_url, list_media, remove_background, extract_text, convert_document, build_signed_url, create_folder, list_folders, create_preset, list_presets, get_usage. No mixed conventions or stray camelCase; the naming is highly predictable.
Tool Count5/5
Fourteen tools is well within the ideal 3-15 range for a media asset management server. Each tool earns its place by covering a distinct operation: two upload paths, URL building, listing, image/doc transforms, folders, presets, and usage. Nothing feels redundant.
Completeness4/5
The surface covers upload (both direct and presigned), listing, on-the-fly transforms, image background removal, OCR, document conversion, signed URLs, folders, presets, and usage. Minor gaps exist: there's no delete for assets or presets, and no get-single-asset or text search, but these are either explicitly explained (folders can't be deleted via API) or workable via listing.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues