Sleek MCP server

Let Claude Code, Cursor or Codex design your mobile app's screens before they code them.

Sleek is an AI mobile app design tool. Its official MCP server gives your coding agent a design step: it sends Sleek your app idea, Sleek designs real iOS and Android screens in an editable project, and your agent builds from those screens instead of improvising a generic AI-looking UI.

Server URL (Streamable HTTP, OAuth sign-in)

https://sleek.design/api/mcp

Connect your client Or set up the agent skill with one prompt

What the Sleek MCP server does

The server is hosted by Sleek, so there is nothing to install. Point your MCP client at one URL, sign in with your Sleek account, and your agent can create projects, run Sleek's design agent, look at the screens it made, and pull each screen's HTML into your codebase.

You describe the whole app in one message, such as a plant shop app with onboarding, home, plant detail, cart, and profile.
Your agent creates a project and sends that brief as a single design run. Sleek plans the screens together, so they share one design system.
The screens appear in the chat, inline or as a rendered image, with a link to the project where you can open and edit them.
Your agent reads each screen's HTML and builds the app in your stack. You can also export the screens to Figma as native layers, to HTML, or to React with Tailwind CSS.

Sleek designs the screens. It does not build or publish your app: your coding agent writes the app code.

Connect your client

Every client uses the same URL and signs in with OAuth. Follow the steps for yours, then sign in to Sleek when prompted.

Claude Code

Run these two commands in your terminal:

claude mcp add --transport http sleek https://sleek.design/api/mcp
claude mcp login sleek

You can also sign in from /mcp inside Claude Code. Or install it as a plugin from the marketplace in the Sleek MCP repository:

/plugin marketplace add sleekdotdesign/mcp
/plugin install sleek@sleek

Cursor

Add Sleek to Cursor with the install link, or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{ "mcpServers": { "sleek": { "url": "https://sleek.design/api/mcp" } } }

Cursor runs the OAuth sign-in when you enable the server, which is all you need.

Codex CLI and ChatGPT desktop

Run these two commands in your terminal:

codex mcp add sleek --url https://sleek.design/api/mcp
codex mcp login sleek

The ChatGPT desktop app, the Codex CLI, and the IDE extension share this configuration.

Claude.ai, Claude Desktop, Cowork, and mobile

On a Pro or Max plan:

Open Customize → Connectors.
Click +, then Add custom connector.
Enter https://sleek.design/api/mcp as 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. Members then find it in Customize → Connectors and click Connect.

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.

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):

{ "mcpServers": { "sleek": { "type": "streamable-http", "url": "https://sleek.design/api/mcp" } } }

Clients that implement MCP authorization discover everything they need from the server and register themselves, so this is usually the whole configuration.

Full client notes, including the API-key fallback, are in the Sleek MCP repository on GitHub.

Authentication: OAuth, no API key needed

Add the URL, your client opens a browser, you approve access. Nothing to copy, nothing to store, and you can revoke it from either side.

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.
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.
To revoke access, remove the connector in your client (in Claude Code, run claude mcp logout sleek), or revoke the grant from your Sleek account.
API keys are a fallback for clients that cannot do OAuth at all. A key from agent setup carries the same access as an OAuth grant and does not expire, so keep it in an environment variable and never commit it.

Tools your agent can call

Your assistant picks the tools for you; this list is for reference. Listing, reading, and rendering are free. Only design runs spend credits.

Sleek MCP server tools, what each does, and what it costs
Tool	What it does	Cost
`list_projects`	List your workspace's projects, newest first. Each project holds one app's screens, theme, and design chat.	Free
`create_project`	Create an empty project to design into. Returns the project and a link where you can watch and edit the designs.	Free
`get_project`	Fetch one project and its link, to confirm it exists and share it with you.	Free
`delete_project`	Permanently delete a project and all its screens. Only after you confirm the exact project by name.	Free, cannot be undone
`list_components`	List a project's screens and their active versions, without the generated HTML.	Free
`get_component`	Fetch a screen's generated HTML, so your agent can build it in your codebase.	Free
`list_references`	List curated app styles with preview images, so the design can follow a look you name.	Free
`design`	Run Sleek's design agent to create or edit screens from a plain-language brief. Send the whole app as one message.	Spends credits
`get_design_run`	Check a design run that is still queued or running, and see which screens it saved.	Free
`cancel_design_run`	Ask a design run to stop, for example when the brief was wrong.	Free (a stopped run is charged only if it saved changes)
`screenshot`	Render up to four screens side by side as one inline image, for clients that cannot show apps.	Free
`show_project`	Show a project's screens inline in the chat, where the client supports apps, so you can enlarge them and open the project in Sleek.	Free

Send the whole app as one design request. Sleek plans the screen set together, so one run for five screens produces a coherent app, while five separate runs produce five unrelated screens and charge five times. The server also lists a few helper tools that only Sleek's own in-chat viewer calls.

Plans and credits

Design runs spend your workspace's AI credits. A new screen costs roughly 30 credits; editing one costs 5 to 30, depending on how much changes.

Sleek plans, their credits, and MCP server access
Plan	Price	Credits	MCP access
Free	$0	60 one-time credits, 1 project, 3 screens	Try it: the trial credits cover about one design run
Starter	$29/mo or $240/yr ($20/mo billed yearly)	3,000 credits/mo, about 100 screens	Not included
Pro	$69/mo or $360/yr ($30/mo billed yearly)	20,000 credits/mo, about 650 screens	Included: MCP server, REST API, and agent skill
Team	$99 per seat/mo or $490 per seat/yr ($40.83 per seat/mo billed yearly)	30,000 credits per seat/mo, about 1000 screens	Included: MCP server, REST API, and agent skill

Free accounts can try the MCP server with their one-time trial credits. Ongoing use requires Pro or Team. Exports to Figma (native layers, no plugin), HTML, and React with Tailwind are included on every plan, including Free. See pricing for plan details and billing questions.

MCP server, agent skill, or REST API?

All three drive the same Sleek service with the same account and credits. Pick the one your client handles best.

MCP server: for clients that support remote MCP servers with OAuth, including Claude Code, Cursor, Codex, Claude, and ChatGPT.
Agent skill: teaches a coding agent Sleek's REST API workflow. The design with AI agents page gives you one prompt that installs it.
REST API: for your own integrations. Read the API reference or the instructions for agents.

Coming from Figma's MCP server? It works with designs that already live in Figma files, while Sleek's server designs new mobile app screens from a brief. They combine well: design in Sleek, then export to Figma as native layers. Our comparison of design MCP servers covers what each one does, and the ranking of AI tools for mobile app design looks beyond agent integrations.

Sleek MCP questions Setup, sign-in, and what it costs.

What is the Sleek MCP server?

It is Sleek's official remote MCP server, at https://sleek.design/api/mcp. It lets Claude Code, Cursor, Codex, Claude, ChatGPT, and other MCP clients design editable iOS and Android app screens in Sleek, show them in the chat, and hand each screen's HTML to your coding agent.

How do I add the Sleek MCP server to Claude Code?

Run "claude mcp add --transport http sleek https://sleek.design/api/mcp", then "claude mcp login sleek" to sign in. You can also sign in from /mcp inside Claude Code.

Do I need an API key?

No. The server uses OAuth: your client opens a browser, you sign in to Sleek, and you approve access. API keys exist only for clients that cannot do OAuth at all.

Is the Sleek MCP server free?

You can try it for free: a new account's one-time trial credits cover about one design run. Ongoing use requires Pro ($69/mo, or $30/mo billed yearly at $360/yr) or Team. Starter does not include MCP or API access. Listing, reading, and rendering screens never spend credits.

Is Sleek an alternative to the Figma MCP server?

They do different jobs. Figma's MCP server works with designs in Figma files. Sleek's MCP server designs new mobile app screens from a written brief. You can use both: design in Sleek, then export the screens to Figma as native, editable layers, with no plugin.

What can I export, and does Sleek build my app?

Screens export to Figma as native layers, to HTML, and to React with Tailwind CSS, on every plan including Free. Sleek designs the screens; it does not build or publish your app. Your coding agent reads each screen's HTML with get_component and builds the app in your own stack.

Should I use the MCP server or the agent skill?

Both use the same Sleek account and credits. Use the MCP server when your client supports remote MCP servers with OAuth. Use the agent skill when you want your coding agent to call Sleek's REST API directly; sleek.design/agents has a one-prompt setup for it.

Why does the server URL show an error in my browser?

The endpoint only accepts POST requests from MCP clients, so opening it in a browser returns 405. Add the URL to your MCP client instead.

Something else? Write to support@sleek.design.

Your agent's first design is free

New accounts include one-time trial credits, enough for your agent's first design. After that, Pro is $69/month, or $30/month billed yearly, with 20,000 monthly AI credits for roughly 650 screens. Cancel anytime.

Connect your agent See pricing details