Design System

app.zakladPublished by zaklad.appOfficial publisherv1.0.0Updated Oct 26, 2026

Build and manage your design system with AI: tokens, themes, components, icons, Figma and code.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP server for building and managing a design system with AI: tokens, themes, components, icons, Figma and code.

What you can do
  • Manage design system tokens, themes, components and icons through the hosted Zaklad platform.
  • Work with design system content alongside Figma and code, as described by the provider.
  • No individual tools are documented, so the exact operations available are not listed.
When to use it
Worth considering if you keep a design system on the Zaklad platform and want an assistant to help build or maintain its tokens, themes, components and icons.
Requirements
A remote endpoint at platform.zaklad.app over streamable HTTP. A bearer token is required in the Authorization header, generated in Project Settings under AI Access.
Before you install
The Authorization header carries a secret bearer token; treat it like a password and keep it out of shared logs. The provider gives no tool list, so what the assistant can read or change is unclear before connecting.

Installation

In SourceWeft

  1. Open Design System in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.zaklad%2Fdesign-system/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "design-system": {
      "type": "http",
      "url": "https://platform.zaklad.app/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.