list_projects
List projects
List 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.
Parameters
limitoffset
Sleek
design.sleekPublished by sleek.designOfficial publisherv1.0.1Updated Oct 24, 2026
Design your mobile app UI with AI, then have your coding agent build the real app from it.
Overview
AI-generated overview
Sleek is a hosted AI mobile app design server that lets an assistant generate, edit, preview and export app screens from a plain-language brief.
- What you can do
- List, create, fetch and permanently delete projects in a Sleek workspace
- List a project's screens and fetch a screen's generated HTML for build handoff
- Browse curated style references to steer the look of a design
- Run the design agent to create or edit screens from one plain-language brief, then poll or cancel the run
- Render up to four screens as one inline image and share the project link
- When to use it
- Useful when you want an assistant to turn a described mobile app into real, editable screens you can open, tweak and export to Figma, HTML or React, and then hand to a coding agent. It suits early UI exploration and design-to-code handoff rather than production asset management.
- Requirements
- Nothing to install: a remote Streamable HTTP endpoint at sleek.design, added to an MCP client. A free Sleek account is needed, and sign-in is normally done with OAuth in the browser. An API key in SLEEK_API_KEY is only a fallback for clients without OAuth. Network access to sleek.design and its authorization server.
Before you install
Design runs spend the workspace's AI credits (roughly 30 per new screen, 5 to 30 per edit); listing, reading and rendering are free, and cancelled runs are not refunded. Approving access lets the client act as you, including spending credits. delete_project permanently removes a project and all its screens and cannot be undone. An API key carries the same power as a full grant, never expires, and should be kept in an environment variable and revoked if leaked.
Installation
In SourceWeft
- Open Sleek in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/design.sleek%2Fsleek/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"sleek": {
"type": "http",
"url": "https://sleek.design/api/mcp"
}
}
}README
Sleek MCP server
Describe a mobile app in plain language and get real, editable screens back, shown right in your chat. Your coding agent can then build the working app from them.
Sleek is an AI mobile app design tool. This is its remote MCP server, which lets Claude, ChatGPT, Codex, Cursor, and any other MCP client design for you: you say "design a plant shop app with onboarding, home, product detail, and cart", and your assistant creates a project, runs the design agent, shows you the screens, and hands you a link where you can open them, edit them, and export them to Figma or code.
There is nothing to install. The server runs on Sleek's infrastructure; you point your client at one URL and sign in.
- New to MCP? It's the open standard that lets an AI client connect to an outside tool. "Remote" means the tool is hosted, so you only need the URL above.
- Need an account? Create one free at sleek.design.
- Want a skill instead of an MCP connection? See sleekdotdesign/agent-skills.
This repository holds only the manifests and docs that point at that server: no server code, no scripts, no hooks, no telemetry.
Quickstart
- Connect your client using the section for it below, and sign in to Sleek when prompted.
- Ask for a whole app in one sentence: "Design a plant shop app in Sleek: onboarding, home with featured plants, plant detail, cart, and profile. Warm, minimal style."
- Your assistant shows you the rendered screens and gives you a project link. Open it to edit, or to export to Figma, HTML, or React.
Send the whole app as one request. Sleek's design agent plans the screen set together, so one message for five screens produces a coherent app; five separate messages produce five unrelated screens and charge you five times.
Connect your client
Every client uses the same URL.
Sign in with OAuth. This is the way to connect Sleek. Add the URL, your client opens a browser, you approve access, done. Nothing to copy, nothing to store, and you can revoke it from either side. Every client on this page supports it, so follow the steps for yours and you are finished.
Do not reach for an API key first. Keys exist only for clients that cannot do OAuth at all. A key is a long-lived secret with the same power over your workspace as a full OAuth grant, it does not expire on its own, and configuring one stops your client from ever offering the browser sign-in. If OAuth is failing, fix that rather than working around it; the troubleshooting section covers the usual causes. The API-key steps below are folded away on purpose.
Claude.ai, Claude Desktop, Cowork, and mobile
Custom connectors work on Free (one connector), Pro, Max, Team, and Enterprise plans. Claude connects to Sleek from Anthropic's cloud, not from your device.
On a Pro or Max plan:
- Open Customize → Connectors.
- Click +, then Add custom connector.
- Enter
https://sleek.design/api/mcpas the remote MCP server URL. - Leave Advanced settings empty. Claude registers itself with Sleek automatically.
- Click Add, sign in to Sleek, and approve access.
On Team or Enterprise, an Owner adds it once under Organization settings → Connectors → Add (hover Custom, select Web, same URL). Members then open Customize → Connectors, find the entry the Owner added, and click Connect.
To disconnect, open Customize → Connectors and choose Remove.
Optional: pre-registered OAuth client ID
If a form insists on a client ID, use the one below and leave the client secret blank. It is a public client, so there is no secret.
Claude Code
You can also sign in from /mcp inside Claude Code.
Or install it as a plugin from the marketplace in this repository:
Then sign in the same way. The plugin's server appears as plugin:sleek:sleek. It ships only the server definition in .mcp.json: no hooks, skills, agents, or commands.
Last resort: API key instead of OAuth
Put the key in your shell profile first, so the value is never written into Claude Code's config:
The single quotes matter: they store the ${SLEEK_API_KEY} reference and Claude Code reads it from your environment on each connection. With double quotes your shell substitutes the key and Claude Code saves it in plain text.
Codex CLI and ChatGPT desktop
The ChatGPT desktop app, the Codex CLI, and the IDE extension share this configuration.
Last resort: API key instead of OAuth
Set SLEEK_API_KEY in your environment, then either:
or add this to ~/.codex/config.toml to apply it to every project:
ChatGPT
- Open Settings → Security and login and turn on Developer mode. Availability depends on your account and workspace policy.
- Go to the ChatGPT Plugins page and click the plus button.
- Give it a name (Sleek) and a description.
- Under Connection, enter
https://sleek.design/api/mcp. - Create the connection and sign in to Sleek.
If it asks for an authentication method, choose OAuth and leave the client ID and secret blank.
Cursor
Paste this into your browser's address bar and Cursor offers to install the server:
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
Cursor runs the OAuth sign-in when you enable the server, which is all you need. Only if that is impossible, add a header; Cursor resolves ${env:NAME}:
Any other MCP client
Add a remote server with the Streamable HTTP transport. The exact type value varies by client (http, streamable-http, or omitted):
Clients that implement MCP authorization discover everything they need from the protected resource metadata and register themselves dynamically, so this is usually the whole configuration. Only a client with no OAuth support at all needs "headers": { "Authorization": "Bearer sk_..." } added to it.
What you can ask for
Design a whole app in one message.
Design a plant shop app in Sleek: onboarding, home with featured plants, plant detail, cart, and profile. Warm, minimal style.
Your assistant creates a project, sends the whole brief as a single design run, shows you the new screens inline (or as one rendered image where the client can't display apps), and shares the project link. One run, charged once.
Look at what you already have, for free.
Show me the cart and profile screens from my plant shop project.
Listing, showing, and rendering cost nothing, so browsing your projects never spends credits.
Edit one screen.
On the plant detail screen, move the Add to cart button into a sticky bottom bar and make the price larger.
The agent edits that screen in place instead of creating new ones. This is a design run, so it spends credits.
Export
The screens are real design files, not pictures of an app. Open the project link your assistant gives you and export from there:
- Figma. Click the Figma button and paste into any Figma file. The screens arrive as native, fully editable Figma layers. No plugin needed.
- Code. Export screens as HTML or as React with Tailwind CSS.
Both are on every plan, including Free. You own everything you make, designs and code, and you can use it commercially.
Your assistant can also pull a screen's generated HTML straight into the conversation with get_component, which is handy if you want it to adapt a screen into your own codebase without you leaving the chat.
Pricing
Design runs spend your Sleek workspace's AI credits. Listing, reading, and rendering are free.
A new screen costs roughly 30 credits; editing one costs 5 to 30, depending on how much changes.
Free accounts get one-time trial credits, enough for about one design run. Sustained use needs the Pro plan or higher: $69/month, or $30/month billed yearly at $360/year, with 20,000 monthly AI credits, roughly 650 screens. See sleek.design/pricing for current plans.
Tools
Your assistant can call twelve tools. It picks them for you; this table is for reference.
The server's tools/list returns fifteen tools, so some clients list three more: open_sleek, get_project_view, and search_mentions. Only Sleek's in-chat screen viewer and ChatGPT's sidebar call these. They are hidden from your assistant, and they're free.
Details that matter if you're driving the tools directly:
designtakes the whole brief as onemessage. Optional:screenIdto edit an existing screen,referenceIdfromlist_referencesto imitate a style,imageUrlsfor visual input,idempotencyKeyso a retry returns the original run instead of charging for a second one, andwait(default true). The wait is capped at 270 seconds; after that the call returnsrunningand you pollget_design_run. Setwaitto false to poll from the start if your client times out sooner.- Every screen has two ids. The
screenIdis the frame on the canvas, and it is whatdesigntakes to edit a screen. The component id, returned asidbylist_components, is whatscreenshotandget_componenttake. A design run returns both for every screen it touches, andlist_componentsandget_componentreturnscreenIdnext to the componentid(nullwhen a component isn't on a canvas). Never pass a component id asscreenId. - Only one design run can be active per project. On a conflict, poll
get_design_rununtil the current run settles, or callcancel_design_run, then retry. - A failed run can include an
error.url. That's where you resolve the problem, usually topping up credits or upgrading. Clients should pass it along. delete_projectrequiresconfirm: true, and should only run after you've named the project you want deleted.- After a design run completes, call
show_projectwith itsrunIdto show what the run made. Fall back toscreenshotonly where the client can't display apps; it renders up to four screens per call, so render more in batches.
Troubleshooting
Claude Code shows sleek as connected before I signed in. That's expected. Sleek lets any client read the server's name and tool list without a login, so the connection succeeds and authentication is only checked when a tool runs. If you skip the sign-in, the first tool call is rejected and Claude Code then marks sleek as needing authentication. Signing in first avoids the round trip.
My API key doesn't work and I never get an OAuth prompt. When you configure an Authorization header, Claude Code treats a rejected key as a failed connection rather than a reason to sign in, so it won't fall back to OAuth. Check the key, or remove the header and use OAuth.
Opening the URL in a browser returns 405. By design. The endpoint accepts POST only; the server is stateless and holds no connection open between calls.
I already have Sleek connected on claude.ai and in Claude Code. Claude Code deduplicates entries pointing at the same URL and keeps one active in /mcp.
To check a key without any client:
Authentication and privacy
The server implements standard MCP authorization with OAuth 2.1: authorization code with PKCE (S256), dynamic client registration, and the scopes openid email profile offline_access. Access tokens last one hour and clients refresh them automatically. Sleek's authorization server is its Supabase Auth instance, named in the protected resource metadata.
What you're granting. Approving the consent screen lets the client act as you in your Sleek workspace: list, create, and delete projects, design and edit screens, and spend the workspace's credits on design runs. It can't do anything your own account can't do.
How to revoke. On the client side, remove the connector (claude.ai: Customize → Connectors → Remove; Claude Code: Clear authentication in /mcp, or claude mcp logout sleek, or claude mcp remove sleek, which also deletes the stored tokens). On the Sleek side, revoke the grant or the API key from your account at sleek.design, or email [email protected].
API keys are the fallback, not the default. A key from sleek.design/agents/setup is a secret carrying the same access as an OAuth grant, with none of its safeguards: it does not expire, it is not bound to a device, and anyone who reads it has your workspace until you revoke it. Use one only where OAuth cannot run. Keep it in an environment variable, never in a file you commit, and revoke it the moment it leaks.
Network. The only destinations are sleek.design and its authorization server. This repository ships no code, no hooks, and no telemetry, and the plugin manifest adds nothing beyond the server definition. What Sleek stores and for how long is in the privacy policy.
Support
Email [email protected], or read the docs for agents. For security reports see SECURITY.md. Maintainers: see docs/publishing.md.
Licensed under the MIT License. See LICENSE.
Source: README.md at commit 597d9e4
Tools
12create_project
Create a project
Create an empty project. Returns it in data, plus projectUrl. Pass data.id as projectId to design, then call screenshot. Creating a project is instant and uses no credits. Only design runs do. Share projectUrl so your user can watch and edit the designs.
Parameters
namerequiredget_project
Get a project
Fetch 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.
Parameters
projectIdrequireddelete_project
Delete a project
Permanently 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.
Parameters
confirmrequiredprojectIdrequiredlist_components
List screens
List 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.
Parameters
limitoffsetprojectIdrequiredget_component
Get a screen's HTML
Fetch 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.
Parameters
projectIdrequiredallVersionscomponentIdrequiredinlineIconslist_references
List design references
List 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.
Parameters
limitoffsetdesign
Design screens with AI
Run 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, share projectUrl with your user and call screenshot.
Parameters
waitmessagerequiredscreenIdimageUrlsprojectIdrequiredreferenceIdidempotencyKeyget_design_run
Get a design run
Poll 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. Share projectUrl and call screenshot. 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.
Parameters
runIdrequiredprojectIdrequiredcancel_design_run
Cancel a design run
Ask 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.
Parameters
runIdrequiredprojectIdrequiredscreenshot
Render screens to an image
Render up to four project screens side by side as one inline image, after a design run completes. 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.
Parameters
scaleformatpaddingprojectIdrequiredbackgroundfullHeightcomponentIdsrequiredsearch_mentions
Search projects to mention
Find 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.
Parameters
queryrequiredVersion history
1- v1.0.1LatestOct 15, 2026
Score
100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts