OAuth-protected access
Connect at the canonical MCP endpoint and approve the scopes and projects the agent needs.
Developer workflow
A screenshot workspace your agent
can operate with clear tools.
Use the remote MCP endpoint to let an agent work on the same projects you open in the browser. Permissions, revisions, assets and render jobs are explicit.
Free during early access ยท No card required
Connect your own agent
One endpoint. The same project.
- Sign in and connect. Add the remote URL in a compatible OAuth-capable MCP client. Approve only the operations and projects you want it to access.
- Give it a concrete brief. Name the app, desired design, device family, target locales and the benefits each screenshot should explain.
- Review the result. Ask for panel previews, resolve missing images or copy, then open the same project in the browser before export.
AI usage is billed by your provider. Available connector settings and attachment transport vary by client. Remote MCP uses OAuth; local REST and stdio clients may use API keys.
Practical walkthrough
Use an inspect, edit, preview loop.
Add the remote endpoint in an MCP client that supports HTTP and OAuth. Authorize the required scopes, then work with stable project and asset IDs rather than assumed filesystem paths.
Discover access and inputs
Read get_access, list the available templates and create or open the intended project. Confirm the output family and localization before editing.
Upload, then bind
Call upload_asset with a supported host attachment reference. Use its persisted key in assign_asset_slot. prepare_upload remains available to clients able to send binary HTTP uploads.
Preview and reconcile
Read get_project after edits. Use preview_panel and resolve missingImages before creating the final render/export. Reread revisions after concurrent browser changes.
Upload and assign
Use upload_asset when the host supplies attachment references, then assign stable asset keys to screenshot slots.
Render after editing
Preview panels, inspect missing inputs and export the completed set only after validation.
Designed for agent loops
The action surface covers project discovery, template choice, panel editing, localization documents, attachment uploads, previews and final artifacts. Responses carry revisions and stable IDs so an agent can reread and reconcile changes.
Use browser and MCP together
Agents are useful for repetitive first passes and localization work. The browser remains the place to visually inspect, adjust and approve the final design.
Questions
Before you start.
What is the MCP URL?
Use https://appscreendesign.com/mcp. The connector discovers OAuth metadata and available actions after you authorize it.
Can MCP clients upload local paths?
Remote clients should pass supported host file references to upload_asset. Local filesystem paths are not assumed to be available to the remote server.
Are API keys required?
Remote MCP uses OAuth. API keys remain available for local or REST clients where that is the better fit.
You built the app.
Give it an introduction.
Start with a composition. Keep every detail editable.