Skip to main content
Version: Next

MCP Server

The Ignix-Lite MCP Server connects your AI assistant directly to the Ignix-Lite engine. It exposes 13 precision tools that let AI agents write, validate, audit, theme, and preview classless semantic HTML without hallucination.

What is MCP?

Model Context Protocol (MCP) is an open standard that allows AI assistants to securely call external tools and data sources.


Quick Start

Install the CLI globally and configure your MCP client:

npm install -g @mindfiredigital/ignix-lite-cli

Then run the auto-setup command for your AI client:

ignix-lite mcp setup cursor

Reload Cursor (Ctrl+Shift+P → Reload Window) to activate.

Try prompts like:

  • Build a login form using Ignix-Lite
  • Validate my HTML index page against Ignix-Lite rules

Available Tools

The Ignix-Lite MCP server exposes 13 precision tools to help you build, validate, audit, and preview interfaces using natural language:

Tool NameCategoryInputsDescriptionExample Prompt
list_componentsDiscoveryNoneLists all 28 available Ignix-Lite components."List all available Ignix-Lite components"
get_manifestDiscoveryname (required)Returns spec (allowed attributes, rules, examples) for a component."What attributes does the toast component support?"
get_emmetDiscoveryname (required)Returns the standard Emmet shorthand pattern for a component."Give me the Emmet shorthand for a dropdown menu"
how_to_buildBuilddescription (required)Converts plain English UI descriptions into HTML and Emmet."Create a danger zone section with a delete button"
generate_themeBuildprompt (required)Generates a custom CSS :root theme from natural language."Generate a dark ocean blue theme"
validateValidationhtml (required)Validates HTML against the classless ruleset."Validate this HTML: <button class='btn'>Click</button>"
check_a11yValidationhtml (required)Audits HTML for WCAG 2.2 AA accessibility violations."Check if my HTML is accessible"
previewPreviewinput (required), optionsRenders HTML/Emmet as a PNG screenshot."Preview my form as a dark mode screenshot at 800px"
get_token_summarySessioncontext_windowReturns token usage statistics for the current session."How many tokens have I used in this session?"
create_handoffSessionrendered_html (required), metadataSaves a state snapshot to pass context between agents/sessions."Save the current dashboard HTML as a snapshot"
apply_handoffSessionhandoff_id (required), changes (required)Patches an existing handoff snapshot with CSS selectors."Update the submit button in handoff hndff_123 to loading"
build_validatedBuilddescription (required), optionsBuild, validate, and audit the accessibility of a layout in a single round-trip."Build and validate a contact form with a submit button"
get_token_costAudithtml (required)Estimate and compare the token size of Ignix-Lite vs Tailwind CSS layout."Compare the token cost of this checkout page HTML"
Validation Rules

Using standard CSS framework classes (e.g. class="..." or variant="...") will fail validation. Always use data-intent and native HTML attributes instead.

AI Workflow Guide

  • Build a UI (Step-by-Step): Use how_to_build to generate, validate and check_a11y to audit, and preview for visual checking.
  • Build a UI (All-in-One): Use the build_validated tool to generate, validate, and audit accessibility in a single command, then use preview to check visually.
  • Validate HTML: Use validate and check_a11y on any existing file content.
  • Multi-agent Hand-off: Save current state with create_handoff and modify with apply_handoff.

Manual Configuration

If you prefer configuring your client manually:

Edit ~/.cursor/mcp.json:

~/.cursor/mcp.json
{
"mcpServers": {
"ignix-lite": {
"command": "node",
"args": ["/path/to/node_modules/@mindfiredigital/ignix-lite-mcp/dist/server.js"]
}
}
}

Core Rules Enforced

The MCP server checks these absolute rules during validation:

AvoidUse Instead
class="..."`data-intent="primary
variant="..." / color="..."data-intent="..."
isLoading={true}aria-busy="true"
isDisabled={true}Native disabled attribute
<div> wrapperSemantic tags like <aside>, <article>, <nav>

Troubleshooting

  • Server not showing: Run the setup command again, verify Node.js v18+ is installed, and fully restart your editor.
  • how_to_build returns no-match: Avoid framework terms (e.g., use primary button instead of React button component).
  • validate fails: Replace classes with data-intent, wrap inputs in label, and use semantic structural tags.
  • preview times out: Ensure Playwright is installed via npx playwright install chromium.