How do I install Slingshot Brand Kit?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Slingshot Brand Kit need an API key?

No required environment variable is listed on this record.

What transport does Slingshot Brand Kit use?

Slingshot Brand Kit runs locally over stdio.

Slingshot Brand Kit

by fyi.slingshot

Slingshot's brand guides, design tokens and an off-brand colour check, for any MCP client.

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Local command

npx -y @slingshot-fyi/[email protected]

Provider

Claude Code

claude mcp add fyi.slingshot-brand-kit -- npx -y @slingshot-fyi/[email protected]

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "fyi.slingshot-brand-kit": {
      "command": "npx",
      "args": [
        "-y",
        "@slingshot-fyi/[email protected]"
      ]
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

Related skills

View all

Questions

How do I install Slingshot Brand Kit?: Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Slingshot Brand Kit need an API key?: No required environment variable is listed on this record.
What transport does Slingshot Brand Kit use?: Slingshot Brand Kit runs locally over stdio.
When was Slingshot Brand Kit last checked?: Last checked 2026-10-16. Slingshot's brand guides, design tokens and an off-brand colour check, for any MCP client.

Slingshot brand kit

Slingshot's own brand, built as an agentic brand system: the same parts the company builds for others, used on itself first. It is the brand behind slingshot.fyi.

Part	What it is
Kit	`brand/`: a router (`readme.md`) and five guides (voice, layout, typography, colour, mark). Every rule carries its reason, so a person or an agent can apply it to a case nobody wrote down.
Tokens	`brand/tokens.json` holds every value once; `dist/tokens.css` is generated from it.
CLI	`slingshot-brand` prints the guides and tokens, and checks files for colours that are not brand tokens.
MCP	`slingshot-brand-mcp` gives any MCP client (Claude Code, Claude Desktop, Cursor) the guides, the tokens and the colour check while it works.

Use it

npx -p @slingshot-fyi/brand-kit slingshot-brand guide            # which guide to read for the task
npx -p @slingshot-fyi/brand-kit slingshot-brand guide voice      # one guide
npx -p @slingshot-fyi/brand-kit slingshot-brand tokens           # tokens as CSS custom properties
npx -p @slingshot-fyi/brand-kit slingshot-brand check src/*.css  # exits 1 if any colour is off-brand

In a clone of this repository, run npm install once and the same commands work as npx slingshot-brand ….

Add the MCP server to Claude Code:

claude mcp add slingshot-brand -- npx -y @slingshot-fyi/brand-kit

It exposes three tools: brand_guide, brand_tokens and check_colors.

How it is tested

npm test checks that every rule has a reason, that the generated CSS covers every token, that the colour check names brand colours and flags the rest, and starts the MCP server to call each tool over stdio.

The kit itself is tested the way Slingshot tests every kit: hand it to a fresh agent with no other context, ask it to make something new, and treat every guess it makes as a missing rule.

Fonts

The statement face, Exposure, is licensed separately and is not in this repository. Geist and Geist Mono are under the SIL Open Font License.

Licence

The code is MIT (see LICENSE). The Slingshot name, mark and copy belong to Slingshot.