Blaze Mobile SDK MCP Server

AI-powered integration assistant for the Blaze Mobile SDK by WSC Sports.

This MCP (Model Context Protocol) server provides contextual SDK guidance directly in your IDE, enabling AI assistants (Cursor, Claude Desktop, VS Code) to give accurate, project-specific help with Blaze Mobile SDK integration on iOS, Android, and React Native.

Supported platforms: iOS (UIKit + SwiftUI), Android (Views + Compose), React Native
Planned: Flutter

Versioning

The MCP server (@wscsports/blaze-mobile-sdk-mcp) is published independently from the native SDK releases. Pin to a major.minor version using ~ so you get MCP fixes without pulling in docs for a newer release you have not validated:

MCP Configuration JSON

{
  "mcpServers": {
    "blaze-mobile-sdk": {
      "command": "npx",
      "args": ["-y", "@wscsports/blaze-mobile-sdk-mcp@~0.1"]
    }
  }
}

When upgrading the MCP package, replace 0.1 with the major.minor of your installed @wscsports/blaze-mobile-sdk-mcp.

Setup

Cursor IDE

Add to your project's .cursor/mcp.json the above "MCP Configuration JSON"

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows) the above "MCP Configuration JSON"

VS Code (with MCP support)

Add to your workspace .vscode/mcp.json the above "MCP Configuration JSON"

What It Does

Once configured, the AI assistant in your IDE can:

• Analyze your project — scans your code for SDK installation, initialization patterns, and common mistakes
• Generate integration code — produces platform-specific initialization and widget code for iOS, Android, and React Native
• Validate integrations — checks existing Blaze SDK setup against structured checklists
• Provide API reference — returns accurate class names, method signatures, delegate protocols, and style structs
• Guide theming — provides style struct and layout reference for stories, moments, and videos
• Troubleshoot issues — diagnoses common problems like widgets not rendering or missing delegates
• Escalate to support — formats a support ticket when an issue needs WSC Sports engineering help

Available Tools

| Tool | Description | |------|-------------| | analyze_project | Scans your project for Blaze SDK integration status | | get_setup_guide | Platform-specific setup instructions | | generate_initialization | Structured init knowledge for one-time SDK setup code | | generate_widget | Structured widget knowledge for widget integration code | | get_widget_guide | Comprehensive widget integration knowledge | | get_style_reference | Style struct and property reference | | get_config_reference | Playback configuration reference | | get_delegate_reference | Delegate and listener protocol reference | | lookup_api_symbol | Look up an API symbol by name | | validate_integration | Validate an existing Blaze SDK integration | | generate_support_ticket | Format a support ticket for WSC Sports escalation |

Resources

| URI | Description | |-----|-------------| | blaze-mobile://quickstart | Quick start guide | | blaze-mobile://api-reference | Auto-generated API reference | | blaze-mobile://widget-comparison | Widget types comparison |

Prompts

| Prompt | Description | |--------|-------------| | setup-blaze-sdk | Guided SDK setup flow | | add-widget | Guided widget addition flow | | troubleshoot | Guided troubleshooting flow |

Example Prompts

After setup, try asking your AI assistant:

• "Set up the Blaze SDK in my iOS SwiftUI app"
• "Initialize Blaze in my Android Compose project"
• "Add a stories row widget with labels data source"
• "Why isn't my widget rendering?"
• "What delegate methods do I need for BlazeWidgetDelegate?"
• "Validate my Blaze SDK integration"
• "Look up BlazeWidgetLayout presets for moments"

Local Development

For contributors working in this repository.

Prerequisites

• Node.js 18+
• npm
• Local clones of Blaze SDK repos (sibling directories or env-var paths) for knowledge regeneration

Setup

git clone https://github.com/WSCSportsEngineering/BlazeSDK-Mobile-Shared.git
cd BlazeSDK-Mobile-Shared/mcp
npm install
npm run bundle

Commands

# Regenerate knowledge from SDK source (per platform)
npm run generate-knowledge -- --platform ios
npm run generate-knowledge -- --platform android
npm run generate-knowledge -- --platform reactnative

# Build single-file bundle
npm run bundle

# Run the server
npm start

# Test with MCP Inspector
npm run inspect

# TypeScript type checking
npm run typecheck

# Run tests
npm test

Regenerating SDK Knowledge

Set the appropriate env var to point at your local SDK repo before running generate-knowledge:

| Platform | Env var | Default sibling path | |----------|---------|----------------------| | iOS | BLAZE_IOS_SDK_PATH | ../BlazeSDK-IOS | | Android | BLAZE_ANDROID_SDK_PATH | ../BlazeSDK-Android | | React Native | BLAZE_RN_SDK_PATH | ../BlazeSDK-ReactNative |

BLAZE_IOS_SDK_PATH=/path/to/BlazeSDK-IOS npm run generate-knowledge -- --platform ios
BLAZE_ANDROID_SDK_PATH=/path/to/BlazeSDK-Android npm run generate-knowledge -- --platform android
BLAZE_RN_SDK_PATH=/path/to/BlazeSDK-ReactNative npm run generate-knowledge -- --platform reactnative

Generated JSON is written to src/knowledge/generated/. Re-run npm run bundle after regenerating.

License

WSC Sports. All rights reserved.