Servidor MCP de Sleek

• Nombre en el registrodesign.sleek/sleekverificado en el registro MCP

El nombre en el registro está bajo sleek.design. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-16
• Herramientas11
• El servidor se llamasleek
• Versión del servidor1.0.1
• Versión del protocolo2025-06-18

El 2026-10-16 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 254 ms.

• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta214 ms
• Espacio en el contexto del agente≈ 2871 tokenslas definiciones de todas sus herramientas (12), que el agente lleva en cada turno
• Definiciones de herramientasA · 100 de 100

• Todas las herramientas pasan las seis comprobaciones.

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. El estado de los servidores MCP de los proveedores: método y números →

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