AppScreenshotStudio MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to AppScreenshotStudio brief, generation and export tools: Does free briefing remain distinct from paid generation and exported marketing assets as the tool workflow evolves?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Research-first generation and editing of mobile app-store screenshot sets.

What we know

MCP for generating/editing screenshot projects, uploading simulator captures, generating AI/Pexels backgrounds and rendering store-ready assets.

Maintenance / activity evidence

@appscreenshotstudio/mcp 0.8.8 published 2026-10-02T08:17:39.950Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Project/asset create/update/render authority. Writes: Create/edit persistent projects; Upload images; Generate paid creative assets; Render output.
API key.
Sensitive access: Unreleased app screenshots, Product details, Brand assets

Creative inputs may be confidential and generation consumes credits; review uploaded assets and plan state.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Does free briefing remain distinct from paid generation and exported marketing assets as the tool workflow evolves?

The bounded review of the publisher's documented AppScreenshotStudio brief, generation and export tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Creative inputs may be confidential and generation consumes credits; review uploaded assets and plan state.
Project/asset create/update/render authority.
API key.
Selected app context and images are uploaded to AppScreenshotStudio and may involve LLM/Gemini/Pexels/storage providers.
Reviewed write actions: Create/edit persistent projects; Upload images; Generate paid creative assets; Render output
Sensitive access: Unreleased app screenshots, Product details, Brand assets
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
public repository identity
Generation/edit operations cost credits.
Rendering requires an active paid plan.
Image inputs have size/count limits.
Projects persist until deleted and download links expire.
No public repo was proven.

Original activity observations

@appscreenshotstudio/mcp 0.8.8 published 2026-10-02T08:17:39.950Z

Technical identity

npm/@appscreenshotstudio/mcp

Exact implementation source: https://www.npmjs.com/package/@appscreenshotstudio/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@appscreenshotstudio/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@appscreenshotstudio/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
appscreenshotstudio.com/api
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
appscreenshotstudio.com/docs/mcp
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
appscreenshotstudio.com/docs/api
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
appscreenshotstudio.com/privacy
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
MCP100 setup guide
Publisher-documented install or connect path; prerequisites and any extra host configuration remain required.
publisher install or stdio launch · Publisher instructions
npx -y @appscreenshotstudio/mcp
reviewed install or registration · Claude Code only · MCP100 composed guide
claude mcp add appscreenshotstudio -- npx -y @appscreenshotstudio/mcp
Configure / authenticate
MCP100 setup guide
Set APPSCREENSHOTSTUDIO_API_KEY in the MCP server environment where premium API is required; distinguish MCP registration from optional `install-skill`.
Check connection
Suggested check
Confirm tools, use a non-billed/read-only research action if available.
Remove / uninstall / revoke
MCP100 setup guide
If registered in Claude Code under the name `appscreenshotstudio`, remove the client entry with `claude mcp remove appscreenshotstudio`. For other MCP hosts remove the matching server/connector in that host’s MCP settings. Remove a globally installed software package separately if applicable; this does not delete data or revoke a service credential.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove appscreenshotstudio

Official Documentation & Sources

What it does

MCP for generating/editing screenshot projects, uploading simulator captures, generating AI/Pexels backgrounds and rendering store-ready assets.

Capability: Design & Creative
Resource type: MCP Server
Industry: Media & Marketing
Best fit: Research-first generation and editing of mobile app-store screenshot sets.

Representative uses

Generate screenshot narrative/projects
Upload raw screenshots/reference images
Edit selected cards
Create panoramic/AI backgrounds
Render high-resolution store PNGs

Limitations

Generation/edit operations cost credits.
Rendering requires an active paid plan.
Image inputs have size/count limits.
Projects persist until deleted and download links expire.
No public repo was proven.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: API key.
Permissions: Project/asset create/update/render authority.
Data handling: Selected app context and images are uploaded to AppScreenshotStudio and may involve LLM/Gemini/Pexels/storage providers.
Cost: usage_based
Risk and cautions: Creative inputs may be confidential and generation consumes credits; review uploaded assets and plan state.

Access scope and cautions

Write actions: Create/edit persistent projects Upload images Generate paid creative assets Render output
Sensitive access: Unreleased app screenshots Product details Brand assets
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Generate screenshot narrative/projects; Upload raw screenshots/reference images; Edit selected cards; Create panoramic/AI backgrounds; Render high-resolution store PNGs.

What setup and authentication are documented?

Recorded installation/entrypoint step: claude mcp add appscreenshotstudio -- npx -y @appscreenshotstudio/mcp. Recorded transport: stdio. Recorded environment-variable notes: APPSCREENSHOTSTUDIO_API_KEY. No configuration values are supplied here. Prerequisites: MCP client; paid plan for rendering. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: API key from AppScreenshotStudio settings.

Can it modify data or perform write operations?

Documented write actions include: Create/edit persistent projects; Upload images; Generate paid creative assets; Render output. Recorded permission boundary: Project/asset create/update/render authority.

What data-handling boundary should I consider?

Selected app context and images are uploaded to AppScreenshotStudio and may involve LLM/Gemini/Pexels/storage providers. Recorded sensitive-access context: Unreleased app screenshots; Product details; Brand assets.

What limitations and risks should I check before use?

Creative inputs may be confidential and generation consumes credits; review uploaded assets and plan state. Generation/edit operations cost credits. Rendering requires an active paid plan. Image inputs have size/count limits. Projects persist until deleted and download links expire. No public repo was proven. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is usage based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.

Is this an official MCP?

AppScreenshotStudio is listed as First-party MCP in MCP100’s current evidence.