UNPKG

@spaik/mcp-server-roi

Version:

MCP server for AI ROI prediction and tracking with Monte Carlo simulations

332 lines (278 loc) 13 kB
# Features Documentation - MCP Server ROI ## Core Features ### 1. ROI Prediction Engine The ROI prediction engine aggregates multiple use cases to create comprehensive financial projections. #### How It Works 1. **Use Case Aggregation**: Combines benefits from all use cases 2. **Confidence Levels**: Applies multipliers for conservative/expected/optimistic scenarios 3. **Time-Based Modeling**: Accounts for implementation and ramp-up periods 4. **Financial Calculations**: NPV, IRR, payback period, 5-year ROI #### Key Components - `ROIEngine` class in `/src/core/calculators/roi-engine.ts` - Configurable discount rates and timeline parameters - Automatic assumption generation based on inputs ### 2. Monte Carlo Simulation Parallel processing of risk scenarios using worker threads. #### Features - 10,000+ simulation iterations - Multiple probability distributions (normal, uniform, beta) - Parallel processing with Piscina worker pool - Risk driver identification through correlation analysis #### Configuration ```typescript { adoptionRate: { min: 0.5, max: 1.0, distribution: 'beta' }, efficiencyGain: { min: 0.7, max: 1.3, distribution: 'normal' }, implementationDelay: { min: 0, max: 3, distribution: 'uniform' }, costOverrun: { min: 1.0, max: 1.5, distribution: 'triangular' } } ``` ### 3. Industry Benchmarking Pre-configured benchmark data for common AI implementations. #### Supported Industries - **Financial Services**: Customer service, fraud detection, document processing - **Healthcare**: Medical records, predictive maintenance, data analytics - **Retail**: Customer service, inventory optimization, process automation - **Manufacturing**: Predictive maintenance, inventory, process automation #### Benchmark Metrics - Average ROI percentage - Typical payback period - Adoption rates - Success rates - Confidence factors ### 4. Multi-Project Comparison Side-by-side analysis of multiple AI initiatives. #### Comparison Metrics - ROI percentage - Payback period - Net Present Value (NPV) - Total investment required - Monthly benefits - Risk scores - Implementation complexity #### Features - Automatic ranking by metric - Variance analysis - Insight generation - Recommendation engine ### 5. Quick Assessment Rapid ROI estimation with minimal inputs. #### Use Cases - Initial feasibility studies - High-level budget planning - Stakeholder presentations - Opportunity prioritization #### Input Requirements - Basic volume metrics - Current costs/time - Automation potential (low/medium/high) - Optional industry selection for benchmarks ## Technical Features ### Type Safety - Full TypeScript implementation - Zod runtime validation - Type inference from schemas - Strict null checks ### Performance Optimization - Worker thread pooling for CPU-intensive tasks - Configurable timeouts - Input validation and bounds checking - Efficient cash flow calculations ### Data Persistence - Supabase PostgreSQL integration - JSONB for flexible schema evolution - Indexed queries for performance - Row-level security ready ### Error Handling - Comprehensive try-catch blocks - Meaningful error messages - Validation error details - Graceful degradation ## Extensibility ### Adding New Industries 1. Update `industry-benchmarks.ts` 2. Add benchmark data object 3. Include typical use cases ### Adding New Metrics 1. Extend Zod schemas 2. Update calculation logic 3. Add to comparison tools ### Custom Distributions 1. Extend Monte Carlo worker 2. Add distribution function 3. Update type definitions ## LLM Optimization Services The MCP Server ROI implements a three-agent system with 9 specialized services designed specifically for optimal LLM consumption and interaction. ### Agent 1: Context Optimizer Transforms raw financial data into semantic-rich, hierarchical information optimized for AI understanding. #### 1. ResponseTransformer Service - **Purpose**: Creates executive summaries and natural language headlines - **Location**: `/src/services/context-optimizer/response-transformer.ts` - **Key Features**: - Converts numerical data to human-readable insights - Generates one-sentence headlines from complex calculations - Creates confidence-based summaries - Example: `roi: 8500``"AI investment will deliver exceptional 8,500% ROI in 5 years"` #### 2. InsightEngine Service - **Purpose**: Extracts patterns and generates actionable insights - **Location**: `/src/services/context-optimizer/insight-engine.ts` - **Key Features**: - Pattern detection across use cases - Risk identification and categorization - Opportunity discovery - Success factor analysis - Example: Identifies that "Customer service automation drives 70% of total value" #### 3. MetadataEnricher Service - **Purpose**: Adds contextual information and quality indicators - **Location**: `/src/services/context-optimizer/metadata-enricher.ts` - **Key Features**: - Confidence scoring (0-1 scale) - Data quality assessment - Assumption documentation - Sensitivity analysis - Calculation methodology tracking ### Agent 2: Intelligence Amplifier Adds predictive capabilities and maintains context across tool interactions. #### 4. PredictiveAnalytics Service - **Purpose**: ML-based predictions and pattern matching - **Location**: `/src/services/intelligence-amplifier/predictive-analytics.ts` - **Key Features**: - Success probability calculation (0-100%) - Risk scoring (1-10 scale) - Peer performance comparison - Historical accuracy tracking - Key success factor identification #### 5. CrossToolMemory Service - **Purpose**: Maintains context and learning across tool calls - **Location**: `/src/services/intelligence-amplifier/cross-tool-memory.ts` - **Key Features**: - Conversation ID tracking - Project context preservation - User preference learning - Cross-tool insight sharing - Historical analysis retrieval #### 6. RecommendationEngine Service - **Purpose**: Generates strategic recommendations and next actions - **Location**: `/src/services/intelligence-amplifier/recommendation-engine.ts` - **Key Features**: - Next action generation - Timeline optimization - Success criteria definition - Alternative approach suggestions - Portfolio strategy recommendations ### Agent 3: Experience Harmonizer Adapts responses for optimal consumption by different LLM contexts. #### 7. ResponseAdapter Service - **Purpose**: Dynamic response formatting based on context - **Location**: `/src/services/experience-harmonizer/response-adapter.ts` - **Key Features**: - Token limit management - Progressive disclosure levels (1-5) - Format preference handling - Audience-specific adaptation - Real-time response compression #### 8. ConversationalBridge Service - **Purpose**: Natural language generation and voice optimization - **Location**: `/src/services/experience-harmonizer/conversational-bridge.ts` - **Key Features**: - Executive briefing generation - Technical summary creation - Voice-ready output (TTS optimization) - Conversational tone adaptation - Multi-modal response support #### 9. QualityAssurance Service - **Purpose**: Validates response quality and accuracy - **Location**: `/src/services/experience-harmonizer/quality-assurance.ts` - **Key Features**: - Calculation accuracy verification - Benchmark alignment checking - Recommendation actionability scoring - Response completeness validation - Anomaly detection and correction ## Service Integration Architecture ``` ┌─────────────────────────────────────────────────────────────┐ │ User Query (LLM) │ └─────────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────────┐ │ MCP Tool Execution │ │ (predict_roi, compare_projects, etc.) │ └─────────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────────┐ │ Context Optimizer │ ├─────────────────────────────────────────────────────────────┤ │ 1. ResponseTransformer → Executive summaries │ │ 2. InsightEngine → Pattern detection │ │ 3. MetadataEnricher → Context & confidence │ └─────────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────────┐ │ Intelligence Amplifier │ ├─────────────────────────────────────────────────────────────┤ │ 4. PredictiveAnalytics → Success predictions │ │ 5. CrossToolMemory → Context preservation │ │ 6. RecommendationEngine → Strategic guidance │ └─────────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────────┐ │ Experience Harmonizer │ ├─────────────────────────────────────────────────────────────┤ │ 7. ResponseAdapter → Format optimization │ │ 8. ConversationalBridge → Natural language │ │ 9. QualityAssurance → Accuracy validation │ └─────────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────────┐ │ Optimized Response for LLM │ └─────────────────────────────────────────────────────────────┘ ``` ## Service Configuration ### Global Service Settings ```typescript { "llm_optimization": { "enabled": true, "default_format": "progressive_disclosure", "max_response_tokens": 2000, "enable_ml_insights": true, "enable_voice_mode": false, "confidence_threshold": 0.7 } } ``` ### Per-Tool Service Overrides ```typescript { "predict_roi": { "services": { "response_transformer": { "include_headlines": true }, "insight_engine": { "max_insights": 5 }, "predictive_analytics": { "enable_peer_comparison": true } } } } ``` ## Best Practices ### Use Case Definition - Be specific about current state metrics - Include all relevant costs (not just direct) - Consider quality improvements - Account for scalability needs ### Timeline Planning - Allow 3 months for implementation - Include 3 months ramp-up - Consider phased rollouts - Plan for contingencies ### Risk Assessment - Use Monte Carlo for large projects - Consider multiple scenarios - Document key assumptions - Track actuals vs projections ### LLM Integration - Start with executive summaries for quick understanding - Use progressive disclosure for detailed analysis - Enable ML insights for data-driven predictions - Request voice output for accessibility - Specify token limits to optimize responses