Stitch Wand

io.github.dilshausPublished by GitHub account dilshausv0.1.1Updated Oct 24, 2026

Design token tools for Google Stitch: convert, validate, diff, lint, generate, and export.

VerifiedSTDIODesktop onlyDeveloper Tools Media & Design

Server details

Identifier: io.github.dilshaus/stitch-wand
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account dilshaus for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.dilshaus%2Fstitch-wand.svg)](https://sourceweft.com/mcp/io.github.dilshaus%2Fstitch-wand?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server giving assistants design token tools for Google Stitch: convert, validate, diff, lint, generate and export tokens.

What you can do: Convert design tokens between formats for Google Stitch workflows, such as turning tokens into a form Stitch can use and back again for export. Validate token sets to catch malformed or inconsistent definitions. Diff token sets to see what changed between versions. Lint tokens for style and consistency problems. Generate and export token sets as finished output.
When to use it: Useful when you keep design tokens in version control and want an assistant to check, compare or convert them while working with Google Stitch. Best suited to designers and front-end developers who already maintain a token pipeline and want those checks inside the assistant.
Requirements: Runs as a local process over stdio, installed from the npm package @stitchwand/mcp-server, so a Node.js runtime and npm are needed. It is desktop-only and not available as a web executable. No accounts, API keys, environment variables or headers are declared.

Before you install

The tool list is not published in the manifest, so confirm exactly which operations it exposes before relying on it. Convert, generate and export operations may write files or overwrite existing token files; check where output goes. No credentials are requested, but review the package source before installing.

Installation

In SourceWeft

Open Stitch Wand in the dashboard and add it to a workspace.
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

This repository has no README.

Tools

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

Version history

v0.1.1LatestSep 16, 2026

Score

25% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.