Halo Ds

io.github.Halo-design-systemPublished by GitHub account Halo-design-systemv0.4.1Updated Nov 3, 2026

Props, examples, design tokens and page blocks for the Halo React design system.

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

Halo Ds's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Halo Ds in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Halo Design System]

Halo Design System

An open-source design system for designers and developers: a Figma library and a React component library built from the same design tokens, with light and dark mode.

📖 Docs & component playground: https://halo-design-system.github.io/Halo-design-system/

Status: early development. Foundations, 44 components, 40 illustrations and 20 awards are in place, in Figma and React. Not yet published to npm.

Packages

PackageDescription
@halo-ds/tokensDesign tokens as CSS variables (light + dark), JSON and JS, generated from Figma
@halo-ds/reactReact components
figma-pluginFigma plugin: search every component and place it on the canvas
docsStorybook: live documentation and component playground

Using Halo

bash
npm install @halo-ds/react

That is all the setup: the styles, the design tokens and the Geist font load by themselves when you use a component.

tsx
import { Button } from '@halo-ds/react';

Switch themes with the data-theme attribute on <html>: light (default), dark, or system (follows the OS).

Every token is a CSS variable starting with --halo-, so your own styles can use them too:

css
.card {  background: var(--halo-surface-primary);  color: var(--halo-text-primary);  padding: var(--halo-spacing-md);  border-radius: var(--halo-radius-sm);}

Make it yours

  • Quick: override a few brand variables in your own CSS, loaded after Halo's. No rebuild needed.
  • Full: change the variables in your copy of the Figma file, export them, and rebuild the tokens so design and code match.

The Theming page in Storybook walks through both, with a live example.

Working on Halo

Requirements: Node.js 20+ and pnpm (npm install -g pnpm). The project pins its own Node 24 runtime, which pnpm downloads automatically.

bash
pnpm install     # install dependenciespnpm dev         # build tokens and start Storybook at http://localhost:6006pnpm build       # build every packagepnpm typecheck   # type-check every package

Project structure

packages/  tokens/     figma/ ← Figma variable exports (source of truth)              scripts/build.mjs → dist/tokens.css, tokens.json, index.js  react/      src/ ← componentsapps/  docs/       Storybook (foundations pages + component stories)docs/         design notes (e.g. dark-mode mapping)

Design → code workflow

  1. Design the component in Figma using Halo variables (never raw hex values).
  2. Build it in packages/react/src/components/<Name>/ using the matching CSS variables.
  3. Add a <Name>.stories.tsx so it appears in Storybook.
  4. Review it in Storybook in both light and dark mode.

See CONTRIBUTING.md for details.

License

MIT. The Figma library also includes emojis, icons, flags and brand logos from other open-source projects; see THIRD_PARTY_NOTICES.md for their licences and required credits.

Source: README.md at commit f6f6363

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.4.1LatestNov 3, 2026
  2. v0.4.0Nov 1, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts