by aegisx-platform
AI developer tools for building UIs and APIs: AegisX MCP offers a CRUD code generator, component docs, dev patterns, and
Gives AI assistants access to AegisX UI components, CRUD generators, and API testing tools for rapid development workflow automation.
AegisX MCP is a community-built MCP server published by aegisx-platform that provides AI assistants with tools and capabilities via the Model Context Protocol. AI developer tools for building UIs and APIs: AegisX MCP offers a CRUD code generator, component docs, dev patterns, and It is categorized under developer tools.
You can install AegisX MCP in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
AegisX MCP is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Strong directory entry: AegisX MCP surfaces stars and publisher context so we could sanity-check maintenance before adopting.
I recommend AegisX MCP for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
I recommend AegisX MCP for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
AegisX MCP reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
According to our notes, AegisX MCP benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Useful MCP listing: AegisX MCP is the kind of server we cite when onboarding engineers to host + tool permissions.
According to our notes, AegisX MCP benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
AegisX MCP has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
According to our notes, AegisX MCP benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Useful MCP listing: AegisX MCP is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 56
MCP (Model Context Protocol) server for the AegisX platform. Provides AI assistants with access to AegisX UI components, CRUD generator commands, development patterns, and API contract discovery.
The component, command, and pattern data files are auto-generated from source libraries:
src/data/components.ts - Generated from aegisx-ui componentssrc/data/crud-commands.ts - Generated from aegisx-cli commandssrc/data/patterns.ts - Validated from existing patterns⚠️ DO NOT EDIT MANUALLY - Changes will be overwritten on next sync.
npm install -g @aegisx/mcp
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"aegisx": {
"command": "npx",
"args": ["-y", "@aegisx/mcp"]
}
}
}
Or if installed globally:
{
"mcpServers": {
"aegisx": {
"command": "aegisx-mcp"
}
}
}
| Tool | Description |
|---|---|
aegisx_components_list | List all UI components, optionally filtered by category |
aegisx_components_get | Get detailed info about a specific component |
aegisx_components_search | Search components by name or description |
Example:
Use aegisx_components_get with name="Card" to see the Card component API.
| Tool | Description |
|---|---|
aegisx_crud_build_command | Build a CRUD generation command with options |
aegisx_crud_packages | View available packages (standard, enterprise, full) |
aegisx_crud_files | See what files will be generated |
aegisx_crud_troubleshoot | Get help with common issues |
aegisx_crud_workflow | Get complete workflow for a feature |
Example:
Use aegisx_crud_build_command with tableName="products" and withImport=true to get the command.
| Tool | Description |
|---|---|
aegisx_patterns_list | List all patterns by category |
aegisx_patterns_get | Get a specific pattern with code |
aegisx_patterns_search | Search patterns |
aegisx_patterns_suggest | Get pattern suggestions for a task |
Example:
Use aegisx_patterns_suggest with task="create API endpoint" to get relevant patterns.
| Tool | Description |
|---|---|
aegisx_api_list | List all API endpoints, optionally filtered by feature |
aegisx_api_search | Search endpoints by keyword across paths and methods |
aegisx_api_get | Get detailed contract for a specific endpoint |
aegisx_api_validate | Validate implementation matches documented contracts |
Examples:
# List all endpoints
Use aegisx_api_list to see all documented APIs.
# Search for budget-related APIs
Use aegisx_api_search with query="budget" to find budget endpoints.
# Get contract details
Use aegisx_api_get with path="/api/profile" to see the full contract.
# Validate a feature
Use aegisx_api_validate with feature="user-profile" to check for mismatches.
| Tool | Description |
|---|---|
aegisx_auth_login | Login to API and store access token (default: localhost:3000) |
aegisx_auth_status | Check authentication status and token info |
aegisx_auth_decode_jwt | Decode JWT token to view header, payload, and expiry details |
aegisx_auth_logout | Logout and clear authentication session |
aegisx_api_request | Make authenticated HTTP requests (GET/POST/PUT/PATCH/DELETE) |
aegisx_api_history | View request/response history with filtering |
aegisx_api_clear_history | Clear request history |
Examples:
# Login to API
Use aegisx_auth_login with email and password to authenticate and store token.
# Check authentication status
Use aegisx_auth_status to see current user info and token expiry.
# Decode JWT token
Use aegisx_auth_decode_jwt to inspect token claims and expiration.
# Test protected endpoint
Use aegisx_api_request with method="GET" and path="/api/profile" to call authenticated endpoints.
# View request history
Use aegisx_api_history to see recent API calls with status codes and response times.
Features:
| Resource | Description |
|---|---|
aegisx://design-tokens | Design tokens (colors, spacing, typography) |
aegisx://development-standards | Coding standards and guidelines |
aegisx://api-reference | Backend API conventions |
aegisx://project-structure | Monorepo structure guide |
aegisx://quick-start | Getting started guide |
| Package | Features |
|---|---|
| standard | Basic CRUD, pagination, search, soft delete |
| enterprise | Standard + Excel/CSV import |
| full | Enterprise + WebSocket events |
The sync tool automatically updates data files from source libraries. This runs before each build via the prebuild hook.
cd libs/aegisx-mcp
pnpm run sync # Update data files
pnpm run sync:dry-run # Preview changes without writing
pnpm run sync:verbose # See detailed progress
Note: The sync process extracts component metadata from libs/aegisx-ui, command definitions from libs/aegisx-cli, and validates existing patterns. Manual edits to generated data files will be overwritten on next sync.
cd libs/aegisx-mcp
pnpm install
pnpm run build
The build process automatically runs pnpm run sync before compilation to ensure data files are up to date.
node dist/index.js
Set DEBUG=mcp:* environment variable for verbose logging.
MIT
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.