Ignix MCP Server
The Ignix MCP Server allows AI assistants to interact with Ignix registries. You can browse available components, search for specific ones, and install them directly into your project using natural language.
Quick Start
Select your MCP client and follow the instructions to configure the ignix MCP server.
- Cursor
- VS Code
- Claude Code
- Codex
Run the following command in your project:
npx ignix mcp init --client cursor
Open Cursor Settings → MCP, enable the Ignix server, and restart Cursor.
Try the following prompts:
- Show me all available Ignix components
- Add button and card components
- Create a landing page using Ignix
Run the following command in your project:
npx ignix mcp init --client vscode
Open .vscode/mcp.json and click Start next to Ignix.
Try with GitHub Copilot:
- Show all Ignix components
- Install a hero section
- Build a contact form
Run the following command in your project:
npx ignix mcp init --client claude
Restart Claude Code and run /mcp.
Try:
- List all components
- Add login form
- Build dashboard layout
npx ignix mcp init --client codex
Then manually add:
[mcp_servers.ignix]
command = "npx"
args = ["ignix", "mcp"]
Restart Codex and test prompts.
What is MCP?
Model Context Protocol (MCP) is an open protocol that enables AI assistants to securely connect to external tools and data sources.
With Ignix MCP, your AI assistant can:
- Browse Components — List all available UI components
- Search Components — Find components across registries
- Install via Natural Language — "add login form"
- Install Themes & Templates
- Work with Multiple Registries
How It Works
The MCP server acts as a bridge between your AI assistant, Ignix CLI, and registries.
- Registry Connection → Connects to configured registries
- Natural Language Input → User prompt
- AI Processing → Converts prompt to tool calls
- CLI Execution → Ignix CLI runs commands
- Installation → Components added to project
Available MCP Tools
Project Tools
- get_version → Returns CLI + MCP version
- check_compatibility → Validates environment
- init_project → Initializes project
- create_react_project → Creates a new React + TypeScript + Tailwind project (used in empty directories)
Component Tools
- list_components → List all available components (source of truth)
- search_components → Search components by keyword (recommended before install)
- install_component → Install components into your project
Template Tools
- list_templates → List all available templates (complete pages/layouts)
- search_templates → Search templates by keyword
- install_template → Install templates into your project
Theme Tools
- list_themes → List all available themes
- install_theme → Install themes into your project
Configuration
You can manually configure MCP servers depending on your client.
Cursor
{
"mcpServers": {
"ignix": {
"command": "npx",
"args": ["ignix", "mcp"]
}
}
}
VS Code
{
"servers": {
"ignix": {
"command": "npx",
"args": ["ignix", "mcp"]
}
}
}
Claude Code
{
"mcpServers": {
"ignix": {
"command": "npx",
"args": ["ignix", "mcp"]
}
}
}
Example Prompts
Browse & Search
- Show me all Ignix components
- Find login form
Install
- Add button component
- Install hero section
- Create dashboard layout
Namespaces
- Install @internal/auth-form
- Show components from @ignix
- Build landing page using hero + features
Troubleshooting
MCP Not Responding
- Check MCP configuration
- Restart MCP client
- Ensure Ignix CLI is installed
- Check network access
Registry Issues
- Verify
ignix.config.json - Check registry URL
Installation Failures
- Ensure project is initialized
- Check directory structure
- Verify permissions
- Install dependencies
Empty Project Issue
If MCP fails in an empty directory:
npm create vite@latest .
or
npx create-react-app my-app
Then retry MCP commands.