MCP server

ThemeKit MCP Server: SwiftUI Design Tokens for AI Agents

The ThemeKit MCP server gives an AI coding agent component lookup, code validation and Figma variable import or export for a token-bound SwiftUI design system.

Run
claude mcp add themekit -- npx -y @isamercan/themekit-mcp@latest
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the ThemeKit MCP server?

ThemeKit MCP is the official server for ThemeKit, a SwiftUI design system of 204 token-bound components and 33 theme presets. It exposes 22 tools, including get_component_api, validate_code, a11y_audit, design_via_figma_mcp and export_figma_variables, so an agent writes SwiftUI from real component data, checks the result, and moves design tokens to and from Figma.

ThemeKit is a native SwiftUI design system with 204 token-bound components that re-skin an app from a single accent color. Its MCP server, published as @isamercan/themekit-mcp, gives an AI coding agent 22 tools to look up components, check generated code, and move design tokens to and from Figma.

Every color, typography, spacing, radius and shadow in ThemeKit resolves at runtime from the active theme instead of being hardcoded. Swapping the theme re-skins the whole interface, and the MCP server is how an agent reads and writes that theme data.

What it changes in your workflow

  • get_component_api and search_components return real ThemeKit component signatures, so generated SwiftUI calls an existing component with real modifiers instead of an invented one.
  • validate_code and a11y_audit check generated ThemeKit code before it ships, catching accessibility issues such as missing Dynamic Type or Reduce Motion support.
  • design_via_figma_mcp reads a design through the Figma Dev Mode MCP server and maps it to ThemeKit components for the agent to build from.
  • export_figma_variables and import_figma_variables move the token catalog between ThemeKit's ThemeConfig and Figma Variables, so one side can drive the other.

Setup at a glance

ThemeKit MCP server
Run commandnpx -y @isamercan/themekit-mcp@latest
Transportstdio, started by the client
Clients namedClaude Code, Cursor, Windsurf
Figma readingOptional FIGMA_MCP_URL env entry pointed at the Figma Dev Mode MCP server

Who it is for

Best for

  • SwiftUI teams on iOS or macOS who want generated screens built from real, token-bound components and checked for accessibility.
  • Teams that already keep brand colors as Figma variables and want them driving a live SwiftUI theme.
  • Projects that need a quick re-skin across one of ThemeKit's 33 bundled theme presets.

Not for

  • When the task is turning a Figma frame itself into a SwiftUI spec rather than theming an existing app, Figma Spec MCP exports platform-ready specs and accessibility audits directly.
  • If the stack is shadcn and web components rather than native SwiftUI, the tinte skill installs and previews shadcn themes and presets instead.
  • Go with a token-coverage audit when the question is whether every theme has matching tokens rather than SwiftUI output, the Theme Audit skill checks each theme for missing tokens and contrast failures.
  • Choose a broader Figma route when the job is reading and editing Figma designs directly, Figma Unified MCP reads, creates and exports SwiftUI and other code from Figma.

Use it with UiChemy

ThemeKit themes a native SwiftUI app. UiChemy's Composer instead edits WordPress pages visually inside Elementor or Gutenberg, so pair ThemeKit for the mobile app and Composer for the marketing site that promotes it.