konnexx-dev-mcp: Command for Claude Code

Architecture Review (MCP Package)

You are an architecture review assistant for the konnexx-dev-mcp package. Use this command to review code for compliance with MCP server patterns, TypeScript conventions, and project standards.

Overview

This command reviews:

• ✅ TypeScript/MCP SDK patterns and conventions
• ✅ Code structure and organization
• ✅ Command file structure and consistency
• ✅ Tool definitions and mappings
• ✅ Test coverage and patterns
• ✅ Package configuration

Usage: Simply type Use architecture-review in Cursor AI chat - no parameters needed!

Step 1: Review TypeScript/MCP Patterns

Check MCP SDK Usage

Review src/index.ts for:

1. Proper imports:

   ✅ import { Server } from "@modelcontextprotocol/sdk/server/index.js";
   ✅ import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
   ✅ import { CallToolRequestSchema, ListToolsRequestSchema, Tool } from "@modelcontextprotocol/sdk/types.js";
   

2. Server initialization:

   ✅ const server = new Server({ name: "konnexx-dev-mcp", version: serverVersion }, { capabilities: { tools: {} } });
   ✅ const transport = new StdioServerTransport();
   ✅ await server.connect(transport);
   

3. Request handlers:

   ✅ server.setRequestHandler(ListToolsRequestSchema, async () => { ... });
   ✅ server.setRequestHandler(CallToolRequestSchema, async (request) => { ... });
   

Check for violations:

• ❌ Missing error handling in handlers
• ❌ Not using proper MCP types
• ❌ Incorrect schema definitions

Check TypeScript Patterns

Review for:

1. Type definitions:

   ✅ interface ProjectContext { ... }
   ✅ type ProjectType = "architecture" | "api" | "web" | "mobile" | "unknown";
   ✅ interface MCPConfig { ... }
   

2. Strict typing:

   • ✅ No any types
   • ✅ Proper return types on functions
   • ✅ Type guards where needed

3. Error handling:

   ✅ try/catch blocks for file operations
   ✅ Proper error messages
   ✅ Fallback values where appropriate