-
Notifications
You must be signed in to change notification settings - Fork 1
feat: Add an MCP server #516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
simeonoff
wants to merge
23
commits into
master
Choose a base branch
from
simeonoff/mcp-server
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
835cea5 to
a308d95
Compare
Add designSystem and variant parameters to create_component_theme tool, enabling component themes to use the correct schema (e.g., -bootstrap-schema, -material-schema) based on the user's design system choice. Changes: - Add designSystem and variant parameters (default to material/light) - Pass schema as first parameter to component theme functions - Import schemas module in CSS generator for compilation - Update tool descriptions with design system examples - Add comprehensive tests for different design systems and variants BREAKING CHANGE: All component theme function calls now include schema parameter
- Add MCP Server section to main README.md with overview, quick start, and client setup instructions - Expand src/mcp/README.md with React and Blazor platform support - Document all 8 tools including get_component_design_tokens and create_component_theme - Add 2-5 meaningful prompt examples for each tool - Include setup instructions for VS Code, WebStorm, Claude Desktop, and Cursor - Provide both local development and published package (npx) configuration paths - Rename PLAN.md to ROADMAP.md for clarity - Remove outdated IMPROVEMENTS.md file - Update package.json to remove unused mcp:dev script
Add new MCP tool that retrieves Ignite UI Theming palette colors as CSS variable references with optional contrast and opacity variations. Features: - Retrieves any palette color (primary, secondary, gray, surface, info, success, warn, error) - Supports all shade variants (50-900, A100-A700) - Returns contrast colors via 'contrast' parameter - Applies opacity using CSS relative color syntax - Validates gray colors don't use accent shades This consolidates the planned get_color and get_contrast_color tools from the roadmap into a single, more versatile tool using a contrast boolean flag. Changes: - Add getColorSchema with Zod validation and gray shade validation - Implement handleGetColor handler with usage examples - Register get_color tool in MCP server - Update ROADMAP.md to reflect tool consolidation and progress
- add `licensed` parameter to all theming tools for Angular projects - update Sass generator to use `@infragistics/igniteui-angular/theming` import - enhance platform detection to identify licensed package usage - update tool schemas and parameter descriptions
Adds set_size, set_spacing, and set_roundness tools to the MCP server for controlling component sizing, spacing multipliers, and border-radius factors via CSS variables. This implementation includes: - Global and component-scoped CSS variable overrides. - Semantic size keyword support (small, medium, large) mapped to framework defaults. - New layout documentation resources and detailed tool descriptions. - Comprehensive schema validation and unit tests for the new handlers. Also updates the ROADMAP and README to reflect the new capabilities and resource URIs.
…neration - Add required checklist to get_component_design_tokens for compound components - Mark missing selectors with skip messaging to handle TODO cases gracefully - Update create_component_theme guidance with compound completeness rules - Include canonical combo example demonstrating full multi-call workflow - Update MCP README documentation with compound checklist and example interaction - Ensure guidance reduces model variance for compound component expansion - Add artifact change set with proposal, design, specs, and tasks
…s to main - Archive compound-theme-guidance to openspec/changes/archive/2026-01-29-compound-theme-guidance/ - Sync delta spec changes to main component-theming spec: - MODIFIED: Component token schemas requirement with compound checklist scenarios - MODIFIED: Component theming requirement with compound completeness rules - ADDED: Compound checklist ordering and minimalism requirement - All artifacts complete, all tasks complete, delta specs synced
…components - Refactor component selector infrastructure to support compound component discovery - Update component theme handlers to integrate compound component workflows - Modify component documentation generation script - Update input theme generation with compound component context - Add test coverage for updated selectors and theme generation
- Add date-picker-theme function with comprehensive tokens documentation - Refactor date picker and date range picker compound component selectors - Update input group schema with corrected CSS variable naming - Add related themes for date picker components (flat-button, calendar) - Improve selector mapping for Angular and Web Components platforms
…niteui-theming into simeonoff/mcp-server
- Add file-input compound component with Angular and WC selectors - Expand grid related themes (combo, calendar, select, icon-button variants) - Fix CSS selectors for paginator, grid-summary, and grid-toolbar - Add missing WebComponents selectors for action-strip, paginator, toolbar
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.