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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dchavezp/design-os-migrator-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server