mcp-mockuuups
Related Servers
Alternatives to mcp-mockuuups
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProduct mockup rendering API for e-commerce and print-on-demand. Upload Photoshop PSD templates, render photorealistic mockups by placing your designs onto smart object layers. 9 tools including AI-powered render (no PSD needed), template management, and account info. Supports remote HTTP (OAuth) and local stdio (npx) transports.1,116 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to generate product mockups by integrating with the Dynamic Mockups API. Supports browsing mockup catalogs, creating single or batch renders with design assets, and managing PSD templates.1344 npm1MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables placing app or website screenshots onto realistic 3D device mockups — around 100 devices including iPhones, iPads, MacBook, Apple Watch, Galaxy phone, laptop and monitor — and returning the result as a downloadable PNG link. It also lists available devices with the exact pixel dimensions that fill each screen.MIT
- AlicenseNot gradedqualityBmaintenanceEnables rendering App Store and Google Play screenshots from AppScreen layout JSON and referenced image files, and polling render jobs for status and signed download links.65 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search a design catalogue for fonts, mockups, and assets; retrieve prices and licence details; obtain checkout links; and open free live 3D mockup scenes.MIT
ultramock-mcpDeprecated
AlicenseAqualityDmaintenanceEnables AI agents to create and configure product mockups on ultramock.io using your own logged-in subscription.111MIT
TDQS
Scored across 4 tools
Each tool targets a clearly distinct stage of the workflow: account_status (billing/plan), search_mockups (discovery), create_mockups (rendering), get_renders (polling async results). No two tools overlap in purpose, and descriptions reinforce the boundaries.
Three of four tools use a consistent verb_noun pattern (search_mockups, create_mockups, get_renders). account_status breaks the pattern with a noun_noun form, but it is still readable and unambiguous.
Four tools cleanly cover the mockup rendering lifecycle without redundancy or padding. The count is well matched to the narrow purpose of the server.
The core loop (check credits, search scenes, render, poll results) is fully covered. Minor gaps exist, such as no way to list prior renders or browse available families/tags independently, but agents can work around these via search.