AegisX MCP▌
by aegisx-platform
AI developer tools for building UIs and APIs: AegisX MCP offers a CRUD code generator, component docs, dev patterns, and
Provides AI assistants with access to AegisX UI components, CRUD generator commands, development patterns, and API contract discovery tools. It enables developers to browse component documentation, build generation commands, and test authenticated API endpoints through the Model Context Protocol.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / Frontend developers using AegisX components
- / Teams building CRUD-heavy applications
- / API integration and testing workflows
capabilities
- / Browse AegisX UI component documentation
- / Generate CRUD operations and commands
- / Test authenticated API endpoints
- / Discover API contracts and patterns
- / Build development pattern templates
what it does
Gives AI assistants access to AegisX UI components, CRUD generators, and API testing tools for rapid development workflow automation.
about
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.
how to install
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.
license
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.
readme
@aegisx/mcp
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.
Features
- UI Components Reference - Browse and search 78+ AegisX UI components with full API documentation
- CRUD Generator Commands - Build and execute CRUD generation commands with 23 supported options (100% CLI alignment)
- Development Patterns - Access best practices, code templates, and architecture patterns
- API Contract Discovery - List, search, and validate API contracts across your codebase
- API Testing & Authentication - Login, test protected endpoints, decode JWT tokens, and track request history
- Design Tokens - Reference design tokens for colors, spacing, typography
- Development Standards - Access coding standards and guidelines
Data Synchronization
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.
Installation
NPM (Global)
npm install -g @aegisx/mcp
Claude Desktop Configuration
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"
}
}
}
Available Tools
UI Components
| 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.
CRUD Generator
| 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.
Development Patterns
| 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.
API Contract Tools
| 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.
API Testing & Authentication Tools
| 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:
- ✅ Automatic token management and storage
- ✅ Request/response history (last 50 requests)
- ✅ JWT token decoding and validation
- ✅ Support for custom headers and query parameters
- ✅ Configurable base URL (default: http://localhost:3000)
- ✅ Environment variable support (AEGISX_API_URL)
Available Resources
| 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 |
Component Categories
- data-display - Badge, Card, Avatar, KPI Card, Stats Card, List, Timeline, Progress
- forms - Date Picker, Input OTP, Knob, Popup Edit, Scheduler, Time Slots
- feedback - Alert, Loading Bar, Inner Loading, Splash Screen, Skeleton
- navigation - Breadcrumb, Command Palette, Navbar, Launcher
- layout - Classic Layout, Compact Layout, Enterprise Layout, Empty Layout
- auth - Login Form, Register Form, Reset Password Form, Social Login
- advanced - Calendar, Gridster, File Upload, Theme Builder, Theme Switcher
- overlays - Drawer
CRUD Packages
| Package | Features |
|---|---|
| standard | Basic CRUD, pagination, search, soft delete |
| enterprise | Standard + Excel/CSV import |
| full | Enterprise + WebSocket events |
Development
Sync Data from Source
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.
Build
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.
Test Locally
node dist/index.js
Debug
Set DEBUG=mcp:* environment variable for verbose logging.
License
MIT
FAQ
- What is the AegisX MCP MCP server?
- AegisX MCP is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for AegisX MCP?
- This profile displays 56 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
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
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ 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.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.5★★★★★56 reviews- ★★★★★Hiroshi Torres· Dec 16, 2024
Strong directory entry: AegisX MCP surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Michael Zhang· Dec 4, 2024
I recommend AegisX MCP for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Ishan Khan· Dec 4, 2024
I recommend AegisX MCP for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Harper Menon· Nov 27, 2024
AegisX MCP reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Evelyn Bhatia· Nov 23, 2024
According to our notes, AegisX MCP benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Michael Wang· Nov 23, 2024
Useful MCP listing: AegisX MCP is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Ishan Bhatia· Nov 23, 2024
According to our notes, AegisX MCP benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Kofi Dixit· Nov 7, 2024
AegisX MCP has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Hiroshi Zhang· Oct 26, 2024
According to our notes, AegisX MCP benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Hiroshi Sharma· Oct 18, 2024
Useful MCP listing: AegisX MCP is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 56