Sleek MCP server

• Registry namedesign.sleek/sleekverified in the MCP registry

The registry name sits under sleek.design. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-16
• Tools11
• Server calls itselfsleek
• Server version1.0.1
• Protocol version2025-06-18

On 2026-10-16 the server answered initialize and tools/list without a sign-in. First answer in 254 ms.

• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer214 ms
• Space in an agent's context≈ 2,871 tokensthe definitions of all its tools (12), which an agent carries on every turn
• Tool definitionsA · 100 of 100

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →

• 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.

• create_project

  Create an empty project, then call design and screenshot. Creation is free and instant. Only design runs spend credits. Share projectUrl so your user can watch and edit the designs.

• get_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.

• delete_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.

• list_components

  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…

• get_component

  Fetch a screen's generated HTML. Returns 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…

• list_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.

• design

  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…

• get_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', read…

• cancel_design_run

  Ask a design run to stop, for example when the brief was wrong. A queued run never starts. A running run stops at its next step and stays 'running' until it settles. A run cut short settles as 'failed' with error code 'cancelled', or…

• screenshot

  Render up to four project screens as one inline image, after a design run completes. Rendering is free. Send projectUrl with the image so your user can open and edit the designs.