AppScreenshots DocsConnect an AI tool
Create and edit screenshot projects with AI, review them with browser tools, and export in the website editor.
Connect an AI tool
When MCP is enabled for this AppScreenshots deployment, connect a compatible AI tool to:
https://appscreenshots.net/api/mcpChoose HTTP/Streamable HTTP and OAuth. Sign in with your AppScreenshots account in the browser, select the projects and assets the tool may use, and choose whether it can create projects. No database access or API key is required.
Start with your screenshots
Upload the original screenshots in the website editor. Authorize that project or select individual assets on the consent page. MCP does not expose binary upload tools; a file attached to a chat is not automatically accessible to this service.
Try this prompt:
Create an English App Store screenshot project from an available template using my authorized assets. Use short headlines and a clean layout. Open the editor using available browser tools, inspect screenshots and correct visual issues, then give me the project link for website export.
The connected AI supplies design and copy; MCP saves editable projects. get_project_preview returns the editor link and review instructions, not image bytes. An agent with browser tools can open the editor, inspect screenshots, correct the design through MCP and reload safely to review the latest version. Browser login is separate from MCP OAuth, and unsaved editor changes must be preserved before reload. The user previews and exports through the website editor.
Manage access and limits
Open Settings → Connected AI tools to change selected projects/assets or revoke a connection. The tool cannot access unselected projects. If the website and an AI tool edit the same project at once, reload the latest project before saving conflicting changes.
Browser review does not require Browserless or a background rendering queue. This MCP exposes project tools and browser review guidance, not cloud rendering. Existing project, paid-template, custom-font and batch-export restrictions still apply. Without browser/image tools, the agent should return the editor link and report visual review as pending, rather than claim verification.
Client support
Claude Code, Codex, Gemini CLI, Z Code and Kimi Code offer remote MCP connection flows. Their configuration formats differ; enter the endpoint in the installed client's HTTP/OAuth setup. ChatGPT requires a custom-connection entry available to your account/workspace or a separately published integration. Do not assume every account has that entry.
A client must support Streamable HTTP and browser OAuth. Browser control and visual inspection depend on the client’s own tools. If those are unavailable, use the editable project link to review or upload on the website.