AIOProductOS Studio MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to AIOProductOS scripted product recording through MCP: Do browser recording and uploads remain scoped to the user's app as capture capabilities expand?

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

Best fit

Local product-demo video and screenshot production from a browser session.

What we know

100%-local MCP using browser automation plus ffmpeg to record scripted walkthroughs of the user's own web app with cursor motion, zooms, captions, transitions and screenshots. Output files land locally.

Maintenance / activity evidence

@aioproductoscom/mcp-studio 0.2.3 published 2026-07-17T07:47:58.789Z

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.
Local browser automation plus filesystem media output. Writes: Navigate/click/type in browser; Write screenshots/video files.
Authentication not yet verified.
Sensitive access: Authenticated web UI, Session-visible data, Local output media

Local-only is strong, but browser automation can act inside logged-in applications and recordings can capture sensitive content.

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

All limitations / Review context

Do browser recording and uploads remain scoped to the user's app as capture capabilities expand?

The bounded review of the publisher's documented AIOProductOS scripted product recording through MCP 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.

Local-only is strong, but browser automation can act inside logged-in applications and recordings can capture sensitive content.
Local browser automation plus filesystem media output.
Official package says nothing is uploaded; browser/session and outputs stay local.
Reviewed write actions: Navigate/click/type in browser; Write screenshots/video files
Sensitive access: Authenticated web UI, Session-visible data, Local output media
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.
Uses the user's browser and logged-in session; authenticated app data can appear in recordings.
Requires Playwright Chromium and ffmpeg for full export.
Can navigate/click/type in the target browser as part of recording.
Outputs are local but may capture confidential UI.

Original activity observations

@aioproductoscom/mcp-studio 0.2.3 published 2026-07-17T07:47:58.789Z

Technical identity

npm/@aioproductoscom/mcp-studio

Exact implementation source: https://www.npmjs.com/package/@aioproductoscom/mcp-studio ↗
Reviewed resource type: MCP Server
Repository identity: AIOProductOS/studio-mcp
Package identity: npm:@aioproductoscom/mcp-studio

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 ↗
@aioproductoscom/mcp-studio
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
aioproductos/studio-mcp
Repository reference; implementation attribution is not established for every document.
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: claude mcp add studio -- npx -y @aioproductoscom/mcp-studio. Requires Node 18+ and Playwright Chromium (npx playwright install chromium) for browser recording.
publisher install or stdio launch · Publisher instructions
npx -y @aioproductoscom/mcp-studio
reviewed install or registration · Claude Code only · MCP100 composed guide
claude mcp add studio -- npx -y @aioproductoscom/mcp-studio
Configure / authenticate
MCP100 setup guide
Node >=18 and Playwright Chromium required for browser-based capture; `npx playwright install chromium`.
Check connection
Suggested check
Check `studio` tools load; do not start export/video capture during connection validation.
Remove / uninstall / revoke
MCP100 setup guide
If registered in Claude Code under the name `studio`, remove the client entry with `claude mcp remove studio`. 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 studio

Official Documentation & Sources

https://www.npmjs.com/package/@aioproductoscom/mcp-studio ↗

What it does

100%-local MCP using browser automation plus ffmpeg to record scripted walkthroughs of the user's own web app with cursor motion, zooms, captions, transitions and screenshots. Output files land locally.

Capability: Design & Creative
Resource type: MCP Server
Industry: Media & Marketing
Best fit: Local product-demo video and screenshot production from a browser session.

Representative uses

Record product walkthroughs
Capture marketing screenshots
Add captions/brand transitions/camera motion
Export MP4/GIF/WebM

Limitations

Uses the user's browser and logged-in session; authenticated app data can appear in recordings.
Requires Playwright Chromium and ffmpeg for full export.
Can navigate/click/type in the target browser as part of recording.
Outputs are local but may capture confidential UI.

Reviewed access

Access & risk

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

Authentication: Not documented in the reviewed sources
Permissions: Local browser automation plus filesystem media output.
Data handling: Official package says nothing is uploaded; browser/session and outputs stay local.
Cost: free
Risk and cautions: Local-only is strong, but browser automation can act inside logged-in applications and recordings can capture sensitive content.

Access scope and cautions

Write actions: Navigate/click/type in browser Write screenshots/video files
Sensitive access: Authenticated web UI Session-visible data Local output media
Risk level: high

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: Record product walkthroughs; Capture marketing screenshots; Add captions/brand transitions/camera motion; Export MP4/GIF/WebM.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @aioproductoscom/mcp-studio. Recorded transport: stdio. Prerequisites: Node 18+; Playwright Chromium; ffmpeg for MP4/GIF. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: No service credential required for local operation.

Can it modify data or perform write operations?

Documented write actions include: Navigate/click/type in browser; Write screenshots/video files. Recorded permission boundary: Local browser automation plus filesystem media output.

What data-handling boundary should I consider?

Official package says nothing is uploaded; browser/session and outputs stay local. Recorded sensitive-access context: Authenticated web UI; Session-visible data; Local output media.

What limitations and risks should I check before use?

Local-only is strong, but browser automation can act inside logged-in applications and recordings can capture sensitive content. Uses the user's browser and logged-in session; authenticated app data can appear in recordings. Requires Playwright Chromium and ffmpeg for full export. Can navigate/click/type in the target browser as part of recording. Outputs are local but may capture confidential UI. 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.