# Drisp [Verified owner] [Health: Active]

**Category:** 📐 Architecture & Design  
**Repository:** https://github.com/drint-io/drisp-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/drisp

## Description
Puts an app or website screenshot on a 3D device mockup (iPhone, iPad, MacBook, Apple Watch, monitor) and returns a PNG.

## Tools
Capabilities this server exposes over MCP:

- **list_devices** — The devices Drisp can put a screenshot on, each with the screenshot size in pixels that fills its screen exactly (portrait for phones, tablets and watches) and its page on drint.io.
- **device_mockup** — Put a screenshot of an app or website on a device mockup and get a PNG. The screenshot fills the screen edge to edge (cropped to the screen's shape if its proportions differ). Give the screenshot as screenshot_url (a public https link) or screenshot_base64 (PNG, JPEG or WebP, at most 10 MB).

## Claude Desktop Quick Installation
No generated config for this server: it installs through its own setup steps.

The project's own setup steps (from https://github.com/drint-io/drisp-mcp), copied verbatim. Run them in order; they are not an mcpServers config.

1. Add to Claude Code:

```sh
claude mcp add --transport http drisp https://drint.io/drisp/mcp
```

2. Run:

```sh
gemini extensions install https://github.com/drint-io/drisp-mcp
```

## Documentation

## What Drisp does

Drisp turns an app or website screenshot into a 3D device mockup and returns a PNG link. Its catalog covers roughly 100 devices, including iPhone models from the 12 through the 18 Pro, iPads, Apple Watch, MacBook, Galaxy phone, laptop, and monitor options. The device frames are rendered with Drint’s 3D rendering engine, including glass and lighting effects.

The screenshot is placed edge to edge inside the selected device display. When the source image and screen have different proportions, the image is cropped to match the screen shape. This makes the service useful for creating product visuals, design previews, and app or website presentation images.

## How it works

Drisp is hosted and accessed over Streamable HTTP at `https://drint.io/drisp/mcp`. There is no local package or process to install. An MCP client connects to the endpoint, calls `list_devices` to inspect available devices and their exact screen-filling screenshot dimensions, then calls `device_mockup` with a chosen device and screenshot.

The screenshot can be supplied as a public HTTPS URL or as base64-encoded PNG, JPEG, or WebP data. Base64 inputs may be up to 10 MB. The generated result is returned as a PNG link that remains available for one hour.

## Setup and configuration

Add the endpoint as a remote or Streamable HTTP MCP server in the client of your choice. Claude, Claude Code, ChatGPT, Cursor, VS Code with GitHub Copilot, Gemini CLI, Codex CLI, Windsurf, and Cline are documented connection options. Claude Code can connect with `claude mcp add --transport http drisp https://drint.io/drisp/mcp`; other clients provide equivalent remote-server settings.

No headers or API key are needed for the unauthenticated connection. Drisp can request a Drint sign-in through OAuth when a clean image or a larger output is selected.

## Tools and capabilities

- `list_devices` returns supported devices, the screenshot dimensions that fill each screen exactly, and the corresponding Drint device page.
- `device_mockup` renders a screenshot on a selected device and returns a PNG link.
- Output sizes include 512 and 1024 pixels; 1536 and 2048 pixels require Drisp Pro.
- Drisp Pro supports clean images without the unauthenticated watermark grid.
- The mockup can use a transparent or colored background and accepts a frame color option.

## Limitations and notes

Without sign-in, results are limited to 1024 pixels, include a light watermark grid, and are limited to about 20 requests per hour per address. Drisp Pro provides clean images up to 2048 pixels and a limit of 60 requests per hour. The service link for each generated picture expires after an hour, so clients should save the PNG if it needs to be retained. Screenshot inputs must use a public HTTPS URL or supported image data within the stated size limit.

_Full upstream README: https://allmcps.com/mcp/drisp/readme_

