MCP X++ Server

# MCP X++ Envisioning Document *Version 1.0 - September 18, 2025* ## Overview This document outlines the strategic vision for extending the MCP X++ server to serve the diverse needs of Dynamics 365 Finance & Operations developers across different roles and responsibilities. ## Current State The MCP X++ server currently provides foundational tools for D365 F&O development: - **Object Creation**: `create_xpp_object`, `create_form` - **Object Discovery**: `find_xpp_object`, `search_objects_pattern`, `inspect_xpp_object` - **Object Modification**: `execute_object_modification`, `discover_modification_capabilities` - **Code Analysis**: `list_code_usages` - **System Management**: `get_current_config`, `build_object_index` ## Target Developer Roles | **Role** | **Primary Activities** | **Current MCP Tools** | **Missing Tools Needed** | **Key Pain Points** | |----------|------------------------|----------------------|---------------------------|---------------------| | **🏗️ Solution Developer** | Create new features, build forms/classes | `create_xpp_object`<br>`create_form`<br>`execute_object_modification`<br>`discover_modification_capabilities` | `validate_architecture`<br>`generate_unit_tests`<br>`check_design_patterns` | Boilerplate code<br>Pattern compliance<br>Test creation | | **🔍 Code Analyst** | Understand existing systems, analyze dependencies | `inspect_xpp_object`<br>`search_objects_pattern`<br>`find_xpp_object`<br>`list_code_usages` | `generate_dependency_graph`<br>`extract_business_logic`<br>`identify_code_smells` | Large codebase navigation<br>Dependency mapping<br>Legacy code understanding | | **🐛 Debugger** | Fix bugs, troubleshoot performance issues | `inspect_xpp_object`<br>`find_xpp_object`<br>`list_code_usages` | `analyze_stack_traces`<br>`trace_execution_flow`<br>`performance_profiler`<br>`find_similar_bugs` | Complex debugging paths<br>Performance bottlenecks<br>Root cause analysis | | **🔧 Maintenance Developer** | Extend and modify existing solutions | `execute_object_modification`<br>`discover_modification_capabilities`<br>`inspect_xpp_object` | `impact_analysis`<br>`breaking_change_detector`<br>`version_compatibility_check` | Breaking existing functionality<br>Complex inheritance<br>Regression prevention | | **📊 Integration Specialist** | Connect D365 with external systems | `create_xpp_object` (entities, services)<br>`inspect_xpp_object` | `create_data_entities`<br>`generate_reports`<br>`validate_json_mapping` | Data mapping complexity<br>Entity design<br>Report creation | ## Current Tools - Detailed Descriptions ### Object Creation Tools #### `create_xpp_object` - **Purpose**: Create any D365 F&O object using dynamic type discovery (544+ object types supported) - **Function**: Generates complete D365 objects with proper metadata structure, dependencies, and layer configuration - **Output**: Fully formed object XML files ready for compilation in Visual Studio 2022 - **Implementation**: Dynamic reflection-based architecture using D365 metadata assemblies for universal object creation #### `create_form` - **Purpose**: Specialized form creation with D365 pattern support and datasource integration - **Function**: Discovers and applies 35+ D365 form patterns dynamically, creates form datasources from table references - **Output**: Forms with proper pattern structure, configured datasources, and D365 UI compliance - **Implementation**: PatternFactory integration with automatic pattern discovery and template application ### Object Discovery Tools #### `find_xpp_object` - **Purpose**: Locate and validate existence of X++ objects by name across all models - **Function**: Searches through metadata cache with optional model and object type filtering - **Output**: Object location details including model, path, and basic metadata - **Implementation**: SQLite-based object index with fast lookup capabilities #### `search_objects_pattern` - **Purpose**: Pattern-based object discovery using wildcards for flexible object exploration - **Function**: Supports * (any characters) and ? (single character) patterns across 544+ object types - **Output**: Filtered object lists with structured JSON or human-readable text formats - **Implementation**: Pattern matching engine with SQLite backend for high-performance searches #### `inspect_xpp_object` - **Purpose**: Deep inspection of D365 objects with progressive disclosure (summary to full details) - **Function**: Four inspection modes - fast summaries, targeted properties, specific collections, and X++ source code extraction - **Output**: Comprehensive object analysis with methods, fields, relations, and metadata - **Implementation**: Dynamic reflection with optimized caching and unlimited collection access ### Object Modification Tools #### `execute_object_modification` - **Purpose**: Batch modification system for D365 objects with per-operation tracking - **Function**: Execute multiple modifications on the same object with individual success/failure tracking - **Output**: Detailed modification results with error reporting for each operation - **Implementation**: Pure reflection architecture using discovered modification capabilities without hardcoded mappings #### `discover_modification_capabilities` - **Purpose**: Real-time discovery of available modification methods for any D365 object type - **Function**: Uses reflection to show what operations (AddField, AddMethod, etc.) are possible for specified object types - **Output**: Complete method signatures with parameter requirements and concrete type names - **Implementation**: Dynamic capability discovery using .NET reflection on D365 metadata assemblies ### Code Analysis Tools #### `list_code_usages` - **Purpose**: Find all references, definitions, and implementations of functions, classes, methods, and variables - **Function**: Comprehensive usage tracking across the entire codebase with optional file path filtering - **Output**: Complete usage lists with file locations, line numbers, and context - **Implementation**: Static code analysis with intelligent symbol recognition and cross-reference indexing ### System Management Tools #### `get_current_config` - **Purpose**: Retrieve server configuration with flexible detail levels for system status and available capabilities - **Function**: Summary view with model names, detailed model information, or complete object type listings (544+ types) - **Output**: Configuration reports with model dependencies, versions, and available object types - **Implementation**: Metadata introspection with optional VS2022 service status checking #### `build_object_index` - **Purpose**: Create and maintain optimized search indexes for faster object discovery - **Function**: Build comprehensive indexes with optional object type filtering and force rebuild capabilities - **Output**: Index statistics and build progress with performance metrics - **Implementation**: SQLite-based indexing system with incremental updates and object type partitioning ## Missing Tools - Detailed Specifications ### 🏗️ Solution Developer Tools #### `validate_architecture` - **Purpose**: Check if new objects follow D365 architectural best practices - **Function**: Analyze class inheritance, naming conventions, layer compliance, dependency injection patterns - **Output**: Architecture compliance report with recommendations - **Implementation**: Static code analysis using D365 metadata APIs #### `generate_unit_tests` - **Purpose**: Auto-create SysTest framework test classes for X++ objects - **Function**: Analyze methods and generate test cases with mock data, assertions, and edge cases - **Output**: Complete test class files ready for execution - **Implementation**: Method signature analysis + SysTest template generation #### `check_design_patterns` - **Purpose**: Validate implementation follows D365 design patterns (Chain of Command, Factory, etc.) - **Function**: Scan code for pattern violations and suggest corrections - **Output**: Pattern compliance score with specific improvement suggestions - **Implementation**: Pattern recognition using AST analysis ### 🔍 Code Analyst Tools #### `generate_dependency_graph` - **Purpose**: Visualize object relationships and dependencies across the entire solution - **Function**: Create interactive graphs showing table relations, class inheritance, method calls - **Output**: Visual dependency maps (SVG/HTML) with drill-down capabilities - **Implementation**: Graph generation using D3.js or similar visualization library #### `extract_business_logic` - **Purpose**: Identify and document business rules embedded in X++ code - **Function**: Parse methods to extract validation rules, calculations, and business workflows - **Output**: Business logic documentation in plain language - **Implementation**: Natural language processing of code comments and logic patterns #### `identify_code_smells` - **Purpose**: Detect anti-patterns and code quality issues - **Function**: Analyze for long methods, duplicate code, complex conditionals, tight coupling - **Output**: Code quality report with refactoring suggestions - **Implementation**: Static analysis with configurable rules engine ### 🐛 Debugger Tools #### `analyze_stack_traces` - **Purpose**: Parse D365 error logs and provide root cause analysis - **Function**: Correlate stack traces with source code, identify common failure patterns - **Output**: Debugging roadmap with likely causes and fix suggestions - **Implementation**: Log parsing + machine learning for pattern recognition #### `trace_execution_flow` - **Purpose**: Follow method execution paths through the entire call chain - **Function**: Generate execution flowcharts showing all possible code paths - **Output**: Interactive execution flow diagrams - **Implementation**: Control flow analysis using metadata APIs #### `performance_profiler` - **Purpose**: Identify performance bottlenecks in X++ code and SQL queries - **Function**: Analyze method complexity, database calls, loop efficiency - **Output**: Performance hotspot report with optimization recommendations - **Implementation**: Complexity analysis + database query parsing #### `find_similar_bugs` - **Purpose**: Pattern-match current issues against known bug database - **Function**: Compare error signatures and code patterns with historical fixes - **Output**: Similar issue matches with proven solutions - **Implementation**: Vector similarity search on error patterns ### 🔧 Maintenance Developer Tools #### `impact_analysis` - **Purpose**: Predict what will break when modifying existing objects - **Function**: Trace all dependencies and usage patterns for changed objects - **Output**: Impact assessment with risk levels and affected components - **Implementation**: Dependency graph traversal + risk scoring algorithm #### `breaking_change_detector` - **Purpose**: Identify modifications that could break existing functionality - **Function**: Compare method signatures, property changes, interface modifications - **Output**: Breaking change report with mitigation strategies - **Implementation**: Semantic versioning analysis + compatibility checking #### `version_compatibility_check` - **Purpose**: Ensure modifications work across different D365 versions/updates - **Function**: Check API compatibility, deprecated method usage, version-specific features - **Output**: Compatibility matrix with upgrade recommendations - **Implementation**: Version-specific metadata comparison ### 📊 Integration Specialist Tools #### `create_data_entities` - **Purpose**: Generate D365 data entities from natural language descriptions, combining multiple related tables - **Function**: Parse business requirements and create comprehensive data entities with proper joins, filters, and field mappings from multiple source tables - **Output**: Complete AxDataEntityView objects with complex data sources, computed fields, relations, and staging configurations - **Implementation**: Natural language processing + table relationship analysis + entity template generation #### `generate_reports` - **Purpose**: Create Electronic Reporting (ER) configurations or SSRS reports from natural language descriptions - **Function**: Parse business requirements and generate complete reporting solutions with data models, formats, and layouts - **Output**: ER configurations with data sources and format mappings, or SSRS report definitions with datasets and layouts - **Implementation**: Natural language processing + D365 reporting framework integration + template generation #### `validate_json_mapping` - **Purpose**: Test data transformation between D365 and external formats - **Function**: Validate field mappings, data type conversions, required fields - **Output**: Mapping validation report with test results - **Implementation**: Schema validation + transformation testing