AegisX

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.

How to use

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.

How to install

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 Desktop

Additional setup and configuration

You 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"]
    }
  }
}

Notes on installation flow and starts

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.

Security and maintenance

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.

Development utilities and data synchronization

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.

Available tools

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.

aegisx_crud_build_command

Build a CRUD generation command with options.

aegisx_crud_packages

View available CRUD packages (standard, enterprise, full).

aegisx_crud_files

See what files will be generated by the CRUD command.

aegisx_crud_troubleshoot

Get help with common issues for CRUD generation.

aegisx_crud_workflow

Get a complete workflow for implementing a feature.

aegisx_patterns_list

List all development patterns by category.

aegisx_patterns_get

Get a specific pattern with code examples.

aegisx_patterns_search

Search development patterns by keyword.

aegisx_patterns_suggest

Suggest patterns for a given task.

aegisx_api_list

List all API endpoints and their features.

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 against documented contracts.

aegisx_auth_login

Login to API and store access token.

aegisx_auth_status

Check authentication status and token info.

aegisx_auth_decode_jwt

Decode JWT token to view header, payload, and expiry.

aegisx_auth_logout

Logout and clear authentication session.

aegisx_api_request

Make authenticated HTTP requests.

aegisx_api_history

View request/response history with filtering.

aegisx_api_clear_history

Clear request history.