Design

sleek.design

This MCP server manages design projects and their screens, enabling creation, retrieval, deletion, and listing of project components and active versions.

1 endpoint11 known toolsFirst detected October 15, 2026Last detected October 16, 2026

ENDPOINT 1

https://sleek.design/api/mcp

No auth detected

MCP server metadata

Name: sleek
Version: 1.0.1

Capabilities

tools.listChanged

Server instructions

Sleek designs mobile app UI with AI. Describe an app and get real, editable screens you can show inline and build the app from. Flow: create_project (or list_projects to reuse one), then design, then screenshot, then share the projectUrl the tools return. That URL is where your user opens, edits, and exports the designs; send it every time, do not just describe what was made. To build the working app, call get_component for each screen and use its HTML as the design source. Send the whole request as ONE design message. The agent plans a screen set together, so a single call for 'onboarding, home, item detail, cart, and profile for a plant shop app' produces a coherent app. Five separate calls produce five unrelated screens and charge for each one. Design runs spend the workspace's AI credits; listing, reading, and rendering are free. Free accounts can try the API with their one-time trial credits (about one design run); sustained use requires the Pro plan or higher ($69/month, or $30/month billed yearly at $360/year, including 20,000 monthly AI credits). One design run at a time per project. On CONFLICT, poll get_design_run until the current run settles (completed or failed), then retry. cancel_design_run asks a run to stop sooner; the project stays locked until the run settles. If a tool returns a URL, send your user there. The API includes one exactly when a human has to act (sign in, upgrade, top up credits), and relaying it is how they unblock you. Auth: connect over OAuth, or send an API key created at https://sleek.design/agents/setup as an "Authorization: Bearer sk_..." header.

Known tools 11

list_projects

List the workspace's projects, newest first.

Inferred read-only

create_project

Create an empty project, then call design and screenshot.

Potential side effects

get_project

Fetch a project and its projectUrl.

Inferred read-only

delete_project

Permanently delete a project and all its screens.

Potential side effects

list_components

List a project's screen names and active version numbers without generated HTML.

Inferred read-only

get_component

Fetch a screen's generated HTML.

Inferred read-only

list_references

List curated app styles and their preview images.

Inferred read-only

design

Run Sleek's design agent to create or edit screens from a plain-language brief.

Potential side effects

get_design_run

Poll a run that design returned as 'queued' or 'running'.

Inferred read-only

cancel_design_run

Ask a design run to stop, for example when the brief was wrong.

Inferred read-only

screenshot

Render up to four project screens as one inline image, after a design run completes.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.sleek]
url = "https://sleek.design/api/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: sleek
Remote MCP URL: https://sleek.design/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "sleek": {
      "type": "http",
      "url": "https://sleek.design/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

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

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.