identityforge-mcp

<p align="center"> <a href="https://identityforge.io"> <img src="https://identityforge.io/opengraph-image.png" alt="Identity Forge branding pipeline from names and design kits to agent-ready systems" width="1200"> </a> </p> <h1 align="center">Identity Forge MCP</h1> <p align="center"><strong>The branding pipeline for the agentic era.</strong></p> <p align="center">Give coding agents a complete design system, then carry it from first build to later updates and client handoff.</p> <p align="center"> <a href="#for-people">For people</a> · <a href="#for-agents">For agents</a> · <a href="#capabilities">Capabilities</a> · <a href="#watch-it-work">Watch it work</a> · <a href="#reference">Reference</a> </p> <p align="center"> <a href="https://www.npmjs.com/package/identityforge"><img src="https://img.shields.io/npm/v/identityforge" alt="npm version"></a> <a href="https://www.npmjs.com/package/identityforge"><img src="https://img.shields.io/npm/dw/identityforge?label=weekly%20downloads" alt="weekly npm downloads"></a> <a href="https://github.com/KasayoDotCom/identityforge-mcp/actions/workflows/ci.yml"><img src="https://github.com/KasayoDotCom/identityforge-mcp/actions/workflows/ci.yml/badge.svg" alt="CI status"></a> <a href="./LICENSE"><img src="https://img.shields.io/npm/l/identityforge" alt="MIT license"></a> </p>

For people

• Start with a complete design kit. Typography, semantic color tokens, layout, spacing, motifs, dos and don'ts, and an implementation-ready DESIGN.md travel together.
• Choose with evidence. Your agent can search the catalog, rank kits for the product and its surfaces, inspect the full brief, and compare nearby directions.
• Apply safely. Identity Forge writes the brief, tokens, and a version stamp, then protects files that changed locally.
• Compose the whole brand. Add an image direction, interface style, and page recipes while keeping the supplied product, person, or object recognizable.
• Carry decisions forward. Version history, drift checks, naming and domain research, saved projects, client shares, and feedback stay in the same workflow.

Public Free kits are ready immediately. An account adds persistent projects, saved work, authenticated quota, and Pro access.

Browse the design kits · See the agent workflow · Read the HTTP API

For agents

Install the local MCP server into your coding agent:

npx --yes identityforge@latest install --client claude-code

Use cursor, vscode, codex, gemini, opencode, or pi in place of claude-code. The installer merges the MCP entry into the client's existing configuration.

Then tell your agent:

Use Identity Forge to pick a theme that fits this product, apply it, and follow the DESIGN.md.

Sign in when you want persistent projects, saved work, authenticated quota, or Pro access:

npx --yes identityforge@latest login

No account yet? In the browser, sign up, complete the security check, select Send verification email, and open its link. Then select Confirm email and continue, approve the resumed authorization, and the CLI receives the key automatically.

Capabilities

Once connected, your agent gets 61 tools grouped around real jobs:

• Find the right system: search, rank, compare, and inspect complete design kits.
• Build from it: export DESIGN.md, CSS, Tailwind v3 or v4, shadcn registry data, DTCG tokens, or JSON.
• Apply and maintain it: preview writes, protect local changes, inspect status, compare versions, and follow drift.
• Direct the presentation: codify image directions, interface styles, and page recipes around the chosen kit.
• Build a client-ready brand: compose variations, generate mockups, share a review link, and act on feedback.
• Name and research: manage a persistent naming board and collect domain, trademark, registra