Sleek
design.sleek/sleekVersion 1.0.1Design your mobile app UI with AI, then have your coding agent build the real app from it.
Status
Responds244 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:24 UTC
- Latency
- 244 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://sleek.design/api/mcpResponds244 msNo sign-in
Claude Code
claude mcp add --transport http sleek https://sleek.design/api/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: sleek
Remote MCP server URL: https://sleek.design/api/mcpCursor
{
"mcpServers": {
"sleek": {
"url": "https://sleek.design/api/mcp"
}
}
}VS Code
code --add-mcp '{"name":"sleek","type":"http","url":"https://sleek.design/api/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
15 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
cancel_design_runAsk a design run to stop, for example when the brief was wrong. Returns the run as it stands right after the request. A queued run comes back 'failed' with error code 'cancelled' and never starts. A running run comes back still 'running' and stops at its next step. A run cut short settles as 'failed' with error code 'cancelled', or 'execution_failed' if saving its changes failed. It keeps any screens and theme changes it saved, listed in data.result.operations, and uses credits only when that list is not empty. A run that finishes before it stops settles as 'completed'. A run that had already settled comes back unchanged. The project stays locked until the run settles, so poll get_design_run before starting another run. A run that stopped responding settles as 'failed' with error code 'execution_timeout' 15 minutes after creation. | Yes | No | Yes | No |
create_projectCreate an empty project. Returns it in data, plus projectUrl. Pass data.id as projectId to design, then call show_project once the run completes. Creating a project is instant and uses no credits. Only design runs do. Share projectUrl so your user can watch and edit the designs. | No | No | No | No |
delete_projectPermanently delete a project and all its screens. Designs cannot be recovered. Call only after your user confirms the exact project by name. Never delete projects to tidy up on your own initiative. | Yes | No | Yes | No |
designRun Sleek's design agent to create or edit screens from a plain-language brief. Send the whole request as ONE message, such as 'a food delivery app with onboarding, restaurants, dish detail, cart, tracking, and profile'. The agent plans the screens together, so separate calls produce mismatched screens. A run uses workspace credits only when it completes or saves changes. By default this waits for the run to finish. If it returns 'queued' or 'running', poll get_design_run. Only one run can be active per project. On CONFLICT, poll get_design_run until the run settles, then retry. cancel_design_run stops it sooner. If a failed run has data.error.url, relay data.error.message to your user with that link. They have to act before you retry. On completion, call show_project with data.runId to show your user what the run made, inline. Use screenshot only where your client cannot show apps. Then share projectUrl with your user. | Yes | No | No | Yes |
get_componentFetch a screen's generated HTML. Returns the screen in data, with the HTML at data.versions[].code. versions holds only the version the screen currently shows. Use allVersions for the full history, which can be large. The returned screenId is the value design takes. Use this for a build handoff, not to check whether a design run worked. | No | Yes | Yes | No |
get_design_runPoll a run that design returned as 'queued' or 'running'. Wait a few seconds between polls. On 'completed', data.result.operations lists the saved screens and theme changes. Call show_project with this runId to show your user what the run made, inline. Use screenshot only where your client cannot show apps. Then share projectUrl. On 'failed', relay data.error.message to your user, with data.error.url if present. A failed run, including a cancelled one, keeps what it saved in that same list and uses credits only when the list is not empty. Check it before resending the brief. | No | Yes | Yes | No |
get_projectFetch a project and its projectUrl. Use it to confirm the project exists and share the URL with your user. Use list_components to see its screens. | No | Yes | Yes | No |
get_project_viewCalled by Sleek's screen viewer to load a project's screens, in canvas order, with their images and the viewer's text. To read screens yourself, use list_components. | No | Yes | Yes | No |
list_componentsList a project's screen names and active version numbers without generated HTML. Pass each item's screenId to design. Pass its id as componentId to get_component or in componentIds to screenshot. Use get_component only when you need a screen's code. | No | Yes | Yes | No |
list_projectsList the workspace's projects, newest first. Each project holds one app's screens, theme, and design chat. Check here before create_project to avoid duplicates. | No | Yes | Yes | No |
list_referencesList curated app styles and their preview images. When your user asks for a look such as Airbnb, brutalist, or dark fintech, pass the closest reference's id as referenceId to design. Without a reference, the agent picks a style. | No | Yes | Yes | No |
open_sleekCalled by ChatGPT's sidebar and Sleek's widget to show the workspace's newest projects, each with a cover. To list projects yourself, use list_projects. | No | Yes | Yes | No |
screenshotRender up to four project screens side by side as one inline image, for clients that cannot show apps. Where your client can, call show_project instead. Returns the image, PNG unless format asks for WebP, and a one-line text note. Rendering uses no credits. Send projectUrl with the image so your user can open and edit the designs. | No | Yes | Yes | No |
search_mentionsFind the workspace's projects by name for an @ mention, newest first. Each item is a resource link whose name is the projectId and whose uri is the projectUrl. To browse every project, use list_projects. | No | Yes | Yes | No |
show_projectShows your user a project's screens inline, in canvas order. They can enlarge a screen, add screens to this chat, and open the project in Sleek. After a design run completes, call it with that runId to show what the run made. Where the client cannot show apps, this returns the screen names only; use screenshot to see the screens. Returns the screen names and ids, the same ones design takes as screenId. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Oct 15, 2026
- Updated
- Oct 15, 2026
- Categories (suggested)
- Project managementDeveloper toolsBrowser automationSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared