home / mcp / aegisx mcp server
Provides AI assistants with access to UI components, CRUD generation, patterns, and API contracts in the AegisX ecosystem.
Configuration
View docs{
"mcpServers": {
"aegisx-platform-aegisx-mcp": {
"command": "npx",
"args": [
"-y",
"@aegisx/mcp"
]
}
}
}You can use the MCP (Model Context Protocol) server from AegisX to access UI components, CRUD generation, development patterns, and API contracts in your AI workflows. It lets you explore components, generate code, discover API contracts, and test authentication, all from a single hosting layer.
You interact with the MCP server through an MCP client or integration that can issue requests to the server. You’ll access UI component metadata, run CRUD commands, retrieve development patterns, and inspect API contracts. Use the server to verify endpoints, view token information, and browse design tokens during development. You can also log in to test protected endpoints and review request history.
Prerequisites: ensure you have Node.js and npm installed on your machine. You will also need access to an MCP client configuration to connect to the server.
# Install the MCP server globally
npm install -g @aegisx/mcp
# Or configure a local development command as shown for Claude DesktopYou can connect to the MCP server using a client configuration. If you install the package globally, you can reference the server binary directly. If you prefer running via a package runner, you can use npx to start the MCP server.
{
"mcpServers": {
"aegisx": {
"command": "npx",
"args": ["-y", "@aegisx/mcp"]
}
}
}If you install the MCP server globally, you can start it with the binary name directly. If you are using the package runner approach, the command shown above (npx -y @aegisx/mcp) will start the server in the same way.
Authenticate to access protected endpoints, review request history, and decode JWT tokens to verify expiry and claims. Keep your design tokens, UI components, and API contracts up to date by synchronizing data as part of your build process to ensure you have the latest data during development.
The MCP data is auto-generated from source libraries. Do not edit generated data manually; the sync step updates components, CRUD commands, and patterns before builds to ensure alignment with your codebase.
List all UI components, optionally filtered by category.
Get detailed info about a specific component.
Search components by name or description.
Build a CRUD generation command with options.
View available CRUD packages (standard, enterprise, full).
See what files will be generated by the CRUD command.
Get help with common issues for CRUD generation.
Get a complete workflow for implementing a feature.
List all development patterns by category.
Get a specific pattern with code examples.
Search development patterns by keyword.
Suggest patterns for a given task.
List all API endpoints and their features.
Search endpoints by keyword across paths and methods.
Get detailed contract for a specific endpoint.
Validate implementation against documented contracts.
Login to API and store access token.
Check authentication status and token info.
Decode JWT token to view header, payload, and expiry.
Logout and clear authentication session.
Make authenticated HTTP requests.
View request/response history with filtering.
Clear request history.