Benefits of Using Solace Event Portal’s MCP Server to Build and Manage Your Event-Driven System

Event-driven architecture (EDA) is powerful, but managing events, schemas, and application relationships can be complex. Solace Event Portal’s MCP Server bridges your AI assistant with Solace Event Portal, enabling developers, architects, and business stakeholders to query, analyze, build and optimize their event-driven systems through natural language.

Event Portal’s MCP Server opens up a plethora of new use case possibilities that can be used to accelerate development, testing, troubleshooting, extending architecture and event explaining the business context of specific EDA use cases to less technical users. Let’s explore a few examples of how different roles can leverage this integration to streamline their workflows.

Developers:
Code Faster, Debug Smarter

Instant Event Schema Lookup

The Challenge: You’re integrating a new microservice and need to understand the structure of your organization’s existing OrderCreated event, including field types, validation rules, and which services publish it.

Without Event Portal MCP Server

• Open Event Portal in browser
• Navigate through domains and applications
• Search for the event catalog
• Review schema documentation
• Switch back to IDE
• Manually construct the data model

With Event Portal MCP Server + AI Assistant

User: “Show me the schema for OrderCreated event and generate a TypeScript interface”

AI Assistant:

• Retrieves schema from Event Portal
• Analyzes field types and constraints
• Generates type-safe interface:

  interface OrderCreated {
  orderId: string;           // UUID format
  customerId: string;
  items: OrderItem[];
  totalAmount: number;       // Decimal, min: 0
  currency: string;          // ISO 4217
  timestamp: Date;
  status: 'pending' | 'confirmed';
  }
  
  Published by: OrderService v2.3.1
  Consumed by: InventoryService, ShippingService, AnalyticsService
  

Result: 5 minutes of context-switching reduced to 30 seconds.

Concept Extension: Prompt your AI coding assistant to implement the OrderCreated event into your current application based on the design requirements inside Event Portal or from another source like a design document.

Troubleshooting Event Flow Issues

The Challenge: Users report order confirmations aren’t triggering. You need to trace the event path from OrderService through the payment gateway to the notification system.

Without Event Portal MCP Server

• Manually browse the application and broker logs
• Manually review design documents
• Manually review Event Portal architecture

With Event Portal MCP Server + AI Assistant

User: “Trace the event flow from OrderService to NotificationService for order confirmations. Review the provided application logs to identify the core reason for failure to create Order Confirmations”

AI Assistant:

Found event flow chain:
1. OrderService → order/confirmed → PaymentQueue
2. PaymentGateway → payment/processed → PaymentCompletedTopic
3. NotificationService subscribes to: payment/processed ✓
4. NotificationService publishes: notification/email/sent ✓

⚠️ Issue detected:
- PaymentGateway v1.8.2 publishes to "payment/completed"
- NotificationService v2.1.0 subscribes to "payment/processed"
- Topic mismatch! PaymentGateway was updated last week.

Recommendation: Update PaymentGateway configuration or NotificationService subscription

Result: Root cause identified in minutes instead of hours of log diving, architecture and implementation analysis.

Concept Extension: Prompt your coding assistant to implement the updates to the applications based on the above discovery, test and create a pull request resolving the issue.

Architects:
Design with Confidence

Impact Analysis for Schema Changes

The Challenge: You need to evolve the CustomerProfile event schema to add GDPR compliance fields, but you must understand the downstream impact before making changes.

Without Event Portal MCP Server

• Search Event Catalog
• Examine each subscribing application
• Review subscribing application codebases
• Understand impact to each application
• Implement the change with proper version management

With Event Portal MCP Server + AI Assistant

User: “What services would be affected if I add a ‘dataRetentionPolicy’ field to CustomerProfile event?”

AI Assistant:

CustomerProfile event analysis:
└─ Currently consumed by 8 services:

High Impact (requires code changes):
├─ RecommendationEngine v3.2 - Uses strict schema validation
├─ DataWarehouse v4.1 - Needs ETL pipeline update
└─ CustomerPortalAPI v2.8 - Reflects all profile fields in UI

Low Impact (backward compatible):
├─ EmailMarketingService v1.5 - Ignores unknown fields
├─ AnalyticsCollector v2.0 - Flexible schema handling
├─ AuditLogger v1.2 - Logs raw event data
├─ CacheInvalidator v1.0 - Only uses customerId field
└─ MetricsAggregator v3.1 - Selective field processing

Recommended Strategy:
1. Add field as optional (backward compatible)
2. Update high-impact services first
3. Version schema to v2.0 after migration complete

Result: Informed decision-making with clear migration path and risk assessment.

Concept Extension: Prompt your AI assistant to implement the dataRetentionPolicy field in a new version of the CustomerProfile schema and event. Create a new version of the subscribing applications to consume the new events and build an update and deploy plan for the high impact applications.

Architecture Optimization Discovery

The Challenge: System performance is degrading. You suspect event topology issues but manually reviewing hundreds of event flows is impractical.

Without Event Portal MCP Server

• Identify potential event candidates by looking through the large catalog.
• Create a list of all applications involved in handling these events.
• Manually review the architecture and implementation of these applications.
• Identify potentially problematic topologies.
• Build a plan to further test and address these issues

With Event Portal MCP Server + AI Assistant

User: “Analyze our event architecture for potential bottlenecks and redundant patterns based on our Solace best practices guide in confluence”

AI Assistant:

Architecture Analysis Complete:

🔴 Critical Issues:
1. Circular dependency detected:
OrderService → InventoryService → PricingService → OrderService
Risk: Potential infinite loops, tight coupling

🟡 Optimization Opportunities:
1. 5 services subscribe to CustomerCreated for logging only
→ Consolidate with centralized AuditService

2. PaymentProcessed event duplicated across 3 queues
→ Use topic with multiple subscriptions

💡 Best Practice Violations:
- 12 events missing version information
- 7 applications publishing to same topic (ambiguous ownership)
- 3 events potentially exceeding recommended payload size (>100KB)

Result: Proactive architecture improvements based on data-driven insights.

Non-Technical Stakeholders:
Visibility Without Complexity

Example 1: Understanding Business Process Flow

The Challenge: A product manager needs to explain the order fulfillment process to the executive team but doesn’t understand the technical event architecture.

Without Event Portal MCP Server

• Email or Slack the lead developer asking how the order fulfillment process works.
• Get ignored for hours, because the lead developer is busy.
• Work his way down the list until a junior developer finally replies with a half-baked, somewhat inaccurate description.

With Event Portal MCP Server + AI Assistant

Product Manager: “Explain our order fulfillment process in business terms, showing which systems are involved”

AI Assistant:

Order Fulfillment Journey:

1. Customer Places Order
   → System: E-commerce Website
   → Creates: Order record

2. Payment Processing (1-2 seconds)
   → System: Payment Gateway
   → Validates: Credit card, fraud check

3. Inventory Check (real-time)
   → System: Warehouse Management
   → Confirms: Product availability
   → Triggers: Item reservation

4. Fulfillment Activation (< 5 minutes)
   → System: Shipping Service
   → Creates: Packing slip, shipping label
   → Notifies: Warehouse staff

5. Customer Notification
   → System: Email & SMS Service
   → Sends: Order confirmation
   → Updates: Order tracking page

Systems Involved: 6 microservices
Based on operational metrics I retrieved from Datadog we find:
Average Processing Time: < 7 minutes
Success Rate: 99.4% (last 30 days)

Result: Business-friendly explanation without technical jargon.

Concept Extension: Provide additional context in the form of written description or documentation pages to allow the AI Assistant to extract operational, logistical or implementation details without having to visit the source code or logging utilities.

Compliance and Audit Reporting

The Challenge: Legal team needs documentation showing how customer data flows through systems for GDPR compliance audit.

With Event Portal MCP Server + AI Assistant

Legal: “Show me all systems that process customer email addresses and how they’re used”

AI Assistant:

Customer Email Data Flow Report:

Data Collection Point:
└─ CustomerRegistration event (source: WebApp, MobileApp)

Systems Processing Email Addresses:

📧 Customer Communication (Purpose: Service delivery)
├─ EmailMarketingService - Promotional emails (user consent required)
├─ NotificationService - Order updates (legitimate interest)
└─ SupportTicketSystem - Customer service (contract fulfillment)

📊 Analytics & Improvement (Purpose: Business analytics)
├─ CustomerInsightsEngine - Behavior analysis (pseudonymized)
└─ ABTestingService - Experience optimization (anonymized)

🔒 Security & Compliance (Purpose: Legal obligation)
├─ FraudDetectionService - Account security
├─ AuditLogger - Compliance tracking (90-day retention)
└─ DataRetentionService - GDPR right-to-erasure handling

✅ Compliance Status:
- All services document legal basis for processing
- Data retention policies: Configured and enforced
- Encryption in transit: TLS 1.3
- Encryption at rest: AES-256
- User consent tracking: Implemented in 3/3 marketing services

Result: Audit-ready documentation generated in seconds, demonstrating compliance posture.

The Power of Contextual AI + Event Portal

The Event Portal MCP Server transforms your AI assistant from a general coding helper or web search alternative into a domain-specific expert that understands your exact event architecture. Instead of generic advice, you get:

• Real-time insights from your actual Event Portal architecture
• Contextual recommendations based on your specific topology
• Instant documentation without manual wiki updates
• Cross-functional communication bridging technical and business language

Getting Started

Integrating Event Portal MCP Server with Claude Desktop, Cline, or other MCP-compatible AI assistants takes minutes:

1. Install the Event Portal MCP Server
2. Configure with your Event Portal credentials
3. Start asking questions in natural language

Whether you’re debugging an event flow at 2 AM, planning a major architecture evolution, or explaining system behavior to stakeholders, your AI assistant becomes an expert teammate who knows your event-driven architecture inside and out.

Ready to supercharge your EDA workflows? Check out the Event Portal MCP Server documentation to get started today.