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 command | npx -y @isamercan/themekit-mcp@latest |
| Transport | stdio, started by the client |
| Clients named | Claude Code, Cursor, Windsurf |
| Figma reading | Optional 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.
Connect ThemeKit MCP Server: SwiftUI Design Tokens for AI Agents to your AI client
claude mcp add themekit -- npx -y @isamercan/themekit-mcp@latestInstall in Claude Code
Run
claude mcp add themekit -- npx -y @isamercan/themekit-mcp@latestso Claude Code starts the server over stdio.Or add it to Cursor or Windsurf
Add the same npx entry shown in the config above to the editor's own MCP settings.
Turn on Figma Dev Mode if needed
In the Figma desktop app, enable the Dev Mode MCP server in Preferences so design_via_figma_mcp has a design source to read.
Point at the Figma server
Set FIGMA_MCP_URL to the Dev Mode server address, by default http://127.0.0.1:3845/mcp.
Check the connection
Ask the agent to call get_component_api for a known component name and confirm it returns real ThemeKit data.
Client configuration
{
"themekit": {
"command": "npx",
"args": ["-y", "@isamercan/themekit-mcp@latest"],
"env": { "FIGMA_MCP_URL": "http://127.0.0.1:3845/mcp" }
}
}Endpoints and ports
http://127.0.0.1:3845/mcpDefault FIGMA_MCP_URL value the Figma desktop app serves on.@isamercan/themekit-mcpPublished npm package the npx command runs.What you can do with it
- Token-bound componentsAll 204 components resolve color, typography, spacing, radius and shadow from the active theme instead of a hardcoded value.
- Code validationvalidate_code checks generated ThemeKit code against the real component API before it ships.
- Accessibility checksa11y_audit runs an accessibility compliance check covering Dynamic Type and Reduce Motion support.
- Figma to SwiftUIdesign_via_figma_mcp reads a design through the Figma Dev Mode MCP server and maps it onto real ThemeKit components.
- Token export to Figmaexport_figma_variables turns the token catalog and theme presets into a Figma Variables library.
- Token import from Figmaimport_figma_variables resolves a company's Figma variables back into a working ThemeConfig.
- 33 bundled presetsA default theme plus 32 ready-made presets inspired by daisyUI give a quick re-skin without hand-picking every color.
- Version migration helpget_migration_guide summarizes the changes between any two ThemeKit releases before an upgrade.
Tools it exposes
get_component_api
Returns a ThemeKit component's real signature and modifiers for the agent to call.
get_design_tokens
Returns the token catalog, including color, typography, spacing, radius and shadow values.
search_components
Finds ThemeKit components by name or category.
validate_code
Checks generated ThemeKit code against the library's real component API.
a11y_audit
Runs an accessibility compliance check on generated ThemeKit code.
design_via_figma_mcp
Reads a design through the Figma Dev Mode MCP server and maps it to ThemeKit components.
export_figma_variables
Builds a Figma Variables library, with one mode per theme preset, from the token catalog.
import_figma_variables
Resolves a Figma file's variables into a ThemeConfig that re-skins every component.
generate_theme
Creates a new theme from a starting color seed.
get_migration_guide
Summarizes what changed between two ThemeKit versions.
Frequently asked questions
What is the ThemeKit MCP server?
It is the official MCP server for ThemeKit, a SwiftUI design system with 204 token-bound components. It gives an AI coding agent tools to look up component data, validate generated code for accessibility, and move design tokens between ThemeKit and Figma.
How do I install the ThemeKit MCP server?
In Claude Code, run claude mcp add themekit followed by the npx command for @isamercan/themekit-mcp@latest. In Cursor or Windsurf, add the equivalent npx entry to the editor's own MCP configuration, then restart the editor.
How does it connect to Figma?
The design_via_figma_mcp tool reads a design through a separate Figma Dev Mode MCP server running locally. Set the FIGMA_MCP_URL environment entry to that server's local address, which Figma assigns by default when Dev Mode is enabled in the Figma desktop app.
Can it check accessibility, not just generate code?
Yes. The a11y_audit tool runs an accessibility compliance check on generated ThemeKit code, and ThemeKit's components themselves support Dynamic Type and Reduce Motion so audited screens can pass those checks without extra custom work.
Can design tokens move both ways between Figma and SwiftUI?
Yes. export_figma_variables turns the ThemeKit token catalog and its presets into a Figma Variables library. import_figma_variables takes a team's own Figma variables and resolves them into a ThemeConfig that re-skins every ThemeKit component.
Which AI coding agents and editors does it work with?
The project names Claude Code, Cursor and Windsurf as supported clients. Any other MCP-compatible editor that can run an npx command over stdio should connect the same way, since the server is a standard MCP server.
How many theme presets does ThemeKit ship with?
It ships 33 presets in total, a default theme plus 32 ready-made color sets inspired by daisyUI. The generate_theme tool can also build a new theme from a single starting color seed instead of picking a preset.


