MCP Server
Asimonim now includes a Model Context Protocol (MCP) server, enabling AI assistants to work with design tokens directly.
Tools
validate_tokens- Validate token files, detect circular references, report deprecated tokenssearch_tokens- Search tokens by name, value, description, or type with regex supportconvert_tokens- Convert tokens to CSS, SCSS, JavaScript, Swift, Android XML, and other formats
Resources
asimonim://tokens- List available token sources with countsasimonim://tokens/{source}- All tokens from a specific sourceasimonim://token/{source}/{path}- Individual token detailasimonim://config- Workspace configuration
Token Discovery
The MCP server reuses the existing token discovery pipeline:
- Local token files from
.config/design-tokens.yaml - npm/jsr dependencies with
designTokensfield or export condition - Resolver documents referenced in config
Usage
# Direct usage
asimonim mcp
# Claude Code plugin
/plugin marketplace add bennypowers/asimonim
/plugin install asimonimClaude Code Plugin
The Claude Code plugin now registers the MCP server alongside the existing LSP, giving AI assistants both editor intelligence and programmatic token access.
Mixed-Schema Workspaces
Alias resolution now uses each token's own schema version rather than a single global version, so workspaces mixing Draft and V2025.10 files resolve JSON Pointer references correctly.