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.
Example prompts:
- Build a landing page using Ignix components
- Find a login form component and install it
- Install the dashboard template into my project
Registries are configured in your project's ignix.config.json file.
{
"registries": {
"@ignix": "https://registry.ignix.dev/{name}.json"
}
}
Quick Start
Cursor
Run:
npx ignix mcp init --client cursor
Then enable the MCP server in Cursor Settings and restart Cursor.
Example prompts:
- Show me all available Ignix components
- Add the button and card components to my project
- Create a landing page using Ignix components
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 the Ignix MCP server, AI assistants can:
- Browse components
- Search components
- Install components using natural language
- Install themes
- Install templates
How It Works
The MCP server acts as a bridge between:
- AI Assistant
- Ignix CLI
- Ignix Registry
- Your Project
Workflow:
-
Registry Connection
MCP connects to Ignix registries. -
Natural Language Input
User writes a prompt such as:Build a restaurant landing page
-
AI Processing
The assistant converts the request into MCP tool calls. -
CLI Execution
Ignix CLI executes the command. -
Component Installation
Components are downloaded and installed in the project.
Available MCP Tools
Project Tools
get_version
Returns the Ignix CLI and MCP version.
check_compatibility
Checks if the environment supports Ignix.
init_project
Initializes an Ignix project configuration.
Registry Tools
list_templates
Lists available templates.
list_themes
Lists available themes.
install_theme
Installs a theme into the project.
Component Tools
list_components
Lists all UI components.
search_components
Searches components by name or metadata.
install_component
Installs a component into the project.
Supported Registries
Ignix MCP supports:
- Ignix official registry
- Third-party registries
- Private company registries
- Namespaced registries
Example:
{
"registries": {
"@ignix": "https://registry.ignix.dev/{name}.json",
"@internal": "https://registry.company.com/{name}.json"
}
}
Example Prompts
Browse components
- Show me all Ignix components
- List available UI components
Search components
- Find a login form component
- Search for navbar component
Install components
- Add button and card components
- Install hero section
Build pages
- Create a landing page
- Build a dashboard layout
- Generate a restaurant landing page
Troubleshooting
MCP Not Responding
- Verify MCP configuration
- Restart the MCP client
- Ensure Ignix CLI is installed
- Check network access
Component Installation Issues
- Verify project initialization
- Check registry configuration
- Confirm file permissions
Empty Project Directory Issue
If MCP tools fail in an empty directory:
- First create a React project
npx create-react-app my-app
or
npm create vite@latest
- Then run Ignix MCP prompts.
Ignix MCP requires an existing project structure.