Is Sleek MCP Server official?
Yes. It's Sleek's own hosted server, documented in the sleekdotdesign/mcp repository.

@Sleek
Basic information
Design your mobile app UI with AI, then have your coding agent build the real app from it.
https://sleek.design/api/mcpclaude mcp add sleek --transport http https://sleek.design/api/mcpList 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Sleek MCP Server is the official hosted MCP server for Sleek, an AI mobile app design tool. You describe an app in plain language, and you get back real, editable mobile app screens rendered as an image in your chat. Your coding agent can then build the app from them.
The server runs on Sleek's infrastructure at https://sleek.design/api/mcp, so there is nothing to install. You sign in with OAuth in your browser. The sleekdotdesign/mcp repository holds only the manifests and docs. It contains no server code.
Create a free account at sleek.design. Then add the URL below to your client and sign in when the browser opens.
https://sleek.design/api/mcp
Sleek recommends OAuth for every client. API keys from sleek.design/agents/setup are only a last resort for clients that can't do OAuth. Configuring a key also stops the client from offering browser sign-in.
claude mcp add --transport http sleek https://sleek.design/api/mcp
claude mcp login sleek
You can also sign in from /mcp, or install the plugin with /plugin marketplace add sleekdotdesign/mcp and then /plugin install sleek@sleek. If you have to use an API key, keep it in an environment variable and use single quotes so Claude Code stores the reference, not the value:
claude mcp add --transport http sleek https://sleek.design/api/mcp \
--header 'Authorization: Bearer ${SLEEK_API_KEY}'
Open Customize → Connectors, click +, choose Add custom connector and enter https://sleek.design/api/mcp. Leave Advanced settings empty, click Add, then sign in to Sleek and approve access. On Team or Enterprise plans, an Owner adds the connector once under Organization settings → Connectors, and members then click Connect.
Add this to ~/.cursor/mcp.json or .cursor/mcp.json. Cursor runs the OAuth sign-in when you enable the server.
{ "mcpServers": { "sleek": { "url": "https://sleek.design/api/mcp" } } }
Add a remote server with a url entry in .vscode/mcp.json and sign in when prompted:
{ "servers": { "sleek": { "type": "http", "url": "https://sleek.design/api/mcp" } } }
codex mcp add sleek --url https://sleek.design/api/mcp
codex mcp login sleek
get_component returns a screen's generated HTML for a build handoff to your coding agent.list_references.The server exposes 11 tools:
list_projects, create_project and get_project. delete_project permanently deletes a project. It needs confirm: true and should run only after the user names the project.list_components lists the screens in a project. get_component fetches a screen's HTML. screenshot renders up to four screens as one image.design takes the whole brief as one message. Optional inputs are screenId, referenceId, imageUrls, idempotencyKey and wait. get_design_run polls a run and cancel_design_run stops one.list_references returns curated app styles to imitate.get_component and build the real app.sleek as connected before you signed in: this is expected. Discovery needs no login, and authentication is checked when a tool runs.POST.get_design_run or call cancel_design_run, then retry.Yes. It's Sleek's own hosted server, documented in the sleekdotdesign/mcp repository.
Free accounts get one-time trial credits, which is enough for about one design run. Sustained use needs the Pro plan or higher. The README lists Pro at $69/month, or $360/year billed yearly, with 20,000 monthly AI credits. A new screen costs roughly 30 credits.
No. OAuth sign-in in the browser is the recommended way. API keys are only for clients that can't do OAuth.
Sleek plans the screen set together. Separate messages produce mismatched screens, and each one is charged as its own run.
Claude (web, desktop and mobile), Claude Code, ChatGPT, Codex, Cursor and any MCP client that supports remote Streamable HTTP servers.
Remove the connector in your client, for example with `claude mcp logout sleek` in Claude Code. You can also revoke the grant or key from your Sleek account.
The Sleek remote MCP server is a hosted Model Context Protocol endpoint at https://sleek.design/api/mcp, so AI assistants can connect to it without installing or running anything locally.
Add the endpoint https://sleek.design/api/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Yes. Sleek uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.
Sleek exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.
Pharmaceutical drug & clinical trial intelligence
The 9apes MCP server lets an AI assistant read the GitHub Actions data 9apes already collects for your organization: runs, jobs, steps, and their durations. Ask it why a build got slower, which jobs take the longest, or
AOI is a commercial environmental-intelligence gateway that gives AI agents programmatic access to 38 real-world intelligence capabilities — climate risk, satellite monitoring, methane detection, water & soil, vegetation
AdaptlyPost: Schedule and publish social posts to Instagram, TikTok, YouTube, X, Facebook, LinkedIn, Pinterest, Threads, and Bluesky from any MCP client.
Understand and troubleshoot your Journeys and Campaigns
Comments