Skip to main content
Glama
Sign In
mtbun

storeshots-mcp

by mtbun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to storeshots-mcp

  • apple-photos-mcp

    sweetrb
    A
    license
    A
    quality
    A
    maintenance
    Enables AI assistants to query and export from the macOS Apple Photos library using natural language, backed by osxphotos.
    21
    1,219 npm
    36
    MIT

Related Servers

  • AppMarquee

    furkangonel
    A
    license
    Not graded
    quality
    D
    maintenance
    A local-first MCP server for creating and managing App Store and Google Play screenshot decks, letting agents upload, review, localize, and export store-ready images without accessing source code.
    MIT

  • StoreShots

    qaimos
    A
    license
    A
    quality
    C
    maintenance
    Turn raw app screenshots into App Store & Google Play marketing screenshots from Cursor, Claude, or any MCP client.
    6
    34 npm
    MIT

  • ShotLingo MCP

    AlperenGuntekin
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables agents to design App Store and Google Play screenshot sets from templates or simulator captures, translate captions into 41 languages with automatic text fitting, render the pixels, and publish straight to App Store Connect or Google Play.
    1
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 6 tools

Disambiguation4/5

Each tool has a distinct scope: discovery (list_presets), single render (compose_screenshot), batch (generate_set), strip (create_showcase), validation (validate_screenshot), full project (build_project). The three rendering tools differ by granularity, and build_project explicitly tells the agent to prefer it over generate_set, which resolves most overlap. Only mild potential confusion remains between generate_set and compose_screenshot.

Naming Consistency5/5

All six tools follow a consistent snake_case verb_noun pattern: list_presets, generate_set, compose_screenshot, create_showcase, validate_screenshot, build_project. The verbs vary appropriately by action while the structural convention is uniform throughout.

Tool Count5/5

Six tools is well-scoped for a screenshot-generation server, covering discovery, single/batch/project rendering, showcase composition, and validation. Each tool earns its place with no redundant entries.

Completeness5/5

The surface covers a full lifecycle: preset discovery, single and batch rendering, whole-project builds with incremental re-render and cleanup of deleted outputs, showcase composition, and store-requirement validation. No obvious gaps in the screenshot-generation domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources