design-os-migration-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sectionsB | List all sections available in a Design OS export package with their component counts and available files |
| read_export_packageA | Read and summarize the entire Design OS export package structure (sections, design system, shell, data model, instructions) |
| read_componentA | Read a specific React component from the export package and return its source code with parsed metadata (imports, Tailwind classes, icon imports, props interface, callbacks) |
| read_export_fileB | Read any file from the Design OS export package by relative path |
| analyze_target_projectA | Analyze a target project to detect its framework, CSS approach, component library, icon library, TypeScript usage, and file conventions |
| read_target_docsA | Read documentation files from the target project. Without a path, lists all available doc files. With a path, returns that file's content. |
| get_migration_contextB | Build a migration mapping between the Design OS export package and the target project, showing what needs to change for colors, icons, CSS, components, imports, file structure, and naming |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| migrate-component | Generate a detailed migration prompt for transforming a single Design OS component to match the target project's conventions |
| migrate-section | Generate a detailed migration prompt for transforming an entire Design OS section (types + all components + tests) to match the target project |
| migrate-design-system | Generate a prompt for translating Design OS design tokens (colors, typography, spacing) into the target project's styling system |
| full-migration | Generate a comprehensive migration plan for the entire Design OS export package into the target project |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: analyzing target project, building migration context, listing export sections, reading components/files from export, reading entire package, and reading target docs. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with underscores (e.g., analyze_target_project, read_component, get_migration_context). The naming is predictable and clear.
7 tools is well-scoped for a migration analysis server. It covers the necessary operations without being excessive or insufficient.
The tool set covers analysis of both source and target, reading various granularities of the export package, and generating migration context. A minor gap is the lack of a tool to apply changes or generate migration scripts, but the set is complete for analysis purposes.