no-api-media-mcp
Related Servers
Alternatives to no-api-media-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables AI image tools directly from Claude Code, Cursor, Windsurf, and other MCP-compatible clients, including vectorization, background removal, upscaling, and logo generation.14 npm1MIT
PopNow MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables ChatGPT, Claude, Cursor, VS Code and other MCP clients to create and edit AI images, videos, songs and voiceovers from plain-language requests, including background removal, upscaling, and effect videos. Connects as a hosted remote server with OAuth 2.1 or API key sign-in, quotes credit prices before generating, and returns results directly in the chat.1MIT- AlicenseAqualityAmaintenanceEnables AI coding clients to generate and save project-aware images and videos using existing paid AI subscriptions, without API keys or passwords, and to optimize media for the web.251Apache 2.0
- AlicenseNot gradedqualityFmaintenanceEnables AI image processing tools such as vectorization, background removal, upscaling, and logo generation from any MCP-compatible client like Claude Code or Cursor.14 npmMIT
- AlicenseAqualityCmaintenanceEnables AI photo generation, editing, and video creation from MCP-compatible clients like Claude Desktop, Cursor, and Windsurf.87 npmMIT

Luw MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI-driven interior, exterior, and landscape design, photoreal rendering, image editing, video generation, and 3D model creation directly inside Claude, Cursor, VS Code, and other MCP clients. It also supports virtual staging, sketching to render, texture and pattern generation, background removal, and architectural consultation through natural language.24149 npmMIT
TDQS
Scored across 25 tools
Most tools occupy a distinct lifecycle slot (brief → generate → audit → compose → deliver → optimize), and descriptions explicitly route between look-alikes such as video_quote vs video_generate and design_brief vs project_profile. The main soft overlaps are social_sizes vs deliver (multi-preset vs single-platform pipeline) and media_optimize vs deliver's built-in compression, which an agent must read carefully to choose correctly.
Tools mix verb_noun (design_brief, composition_check, media_cleanup) with noun_verb (image_generate, video_generate, palette_extract, background_remove), bare nouns (brand_profiles, accounts_status, usage_report), and lone verbs (compose, deliver). Each name is readable in isolation, but there is no single predictable pattern an agent can rely on.
Twenty-five tools is at the heavy boundary for a media pipeline; nearly all serve a real stage (generation, quoting, editing, optimization, delivery, cleanup, accounts), but the surface is broad enough that an agent must scan a lot to find a step. A few (usage_report, loop_check) are niche enough to consider folding in.
The generate → check → compose → deliver → optimize → clean lifecycle is well covered, including cost quoting, brand profiles, and local editing via video_edit. Gaps are minor: image editing is limited to background_remove/social_sizes/deliver, with no general crop/resize/retouch for stills analogous to video_edit.