What is Mymcp

myMCP is a multi-interface fantasy-themed chatbot system designed to gamify real-world skill development through engaging quests. Built on a modern Node.js architecture using TypeScript and Express.js, it offers a unique approach to learning by transforming mundane technical tasks into epic adventures.

Use cases

myMCP is ideal for individuals or teams looking to enhance their technical skills while engaging in a fun and immersive experience. It can serve educational institutions for teaching programming concepts, businesses for training employees on technical tasks, or anyone interested in self-improvement through gamification.

How to use

To get started with myMCP, clone the repository, install the dependencies, and start the engine and CLI in separate terminals. You can then embark on quests to develop skills like timezone coordination or server monitoring, interact in chat, and check your progress through the command-line interface.

Key features

Key features of myMCP include gamified learning through fantasy quests, a modern architecture with a cross-platform capability, support for multiple interfaces (CLI, Web, API, and MCP protocol), real-time updates for game state synchronization, and a structured approach to skill development in technical areas.

Where to use

myMCP can be used in various environments, including educational settings for teaching purposes, corporate training programs for upskilling employees, or personal projects for developers wanting to learn new technologies in a gamified context. It is compatible with Windows, macOS, Linux, and WSL.

myMCP - Fantasy Chatbot System

🗡️ Transform mundane technical tasks into engaging fantasy adventures

A multi-interface fantasy-themed chatbot system that gamifies real-world skill development through epic quests. Features LLM-powered conversations, MCP protocol support, Slack integration, and distributed multiplayer capabilities.

✨ What Makes myMCP Special?

• 🤖 AI-Powered Conversations - Natural language interactions with Anthropic/OpenAI
• 🎮 Gamified Learning - Master real skills through fantasy quests
• 💬 Slack Integration - Play directly from Slack with team dashboards
• 🌟 Multi-Interface - CLI, Web, API, MCP protocol, and Slack
• ⚡ Real-Time Multiplayer - Redis-powered distributed architecture
• 🔧 Production Ready - Docker support, clean architecture, TypeScript

🚀 Quick Start (2 minutes)

Prerequisites

• Node.js 18+ and npm 9+
• Git for version control
• (Optional) Redis for multiplayer features
• (Optional) Anthropic/OpenAI API key for AI conversations

Get Running

# 1. Clone and install
git clone <repository-url>
cd myMCP
npm install

# 2. (Optional) Set up AI - create .env in project root
echo "ANTHROPIC_API_KEY=your-key-here" > .env

# 3. Start the engine
node tools/startup/start-engine.js

# 4. In another terminal, start the interactive CLI
cd packages/cli && npm run shell

Your First Adventure

Adventure> help                    # See available commands
Adventure> status                  # Check your character
Adventure> I want to start a quest # Natural language works!
Adventure> What should I do next?  # Ask your AI guide

🏗️ Project Structure (Reorganized!)

myMCP/
├── packages/              # Monorepo packages
│   ├── engine/           # 🎮 Game engine API (Express + WebSocket)
│   ├── cli/              # 🗡️ Interactive command-line interface
│   ├── mcpserver/        # 🤖 MCP protocol server
│   ├── slack-integration/# 💬 Slack bot and dashboards
│   └── webapp/           # 🌐 React web interface (planned)
├── tools/                # Development tools
│   ├── setup/           # Setup and installation scripts
│   ├── startup/         # Service startup scripts
│   ├── testing/         # Test utilities
│   └── assets/          # Icons and images
├── shared/              # Shared code
│   ├── types/           # TypeScript type definitions
│   ├── utils/           # Common utilities
│   └── config/          # Shared configuration
├── docs/                # Documentation
│   ├── setup/           # Setup guides
│   ├── integrations/    # Integration documentation
│   └── archive/         # Historical documents
└── tests/               # Test suites

🎭 LLM-Powered Fantasy System

Natural Language Understanding

# Instead of memorizing commands...
Adventure> start-quest council-of-three-realms  # Old way

# Just speak naturally!
Adventure> I'd like to help unite the three kingdoms
Adventure> What quests are available for a novice like me?
Adventure> Tell me more about the Council quest

Dynamic AI Responses

Your AI guide adapts based on:

• Current quest progress
• Player level and achievements
• Recent actions and context
• Natural conversation flow

Supported LLM Providers

• Anthropic Claude (Recommended) - Best narrative quality
• OpenAI GPT - Alternative option
• Fallback System - Works without API keys

💬 Slack Integration

Transform your Slack workspace into a fantasy realm!

Features

• 🎯 Slash Commands - /mymcp status, /mymcp quest, /mymcp leaderboard
• 📊 Live Dashboard - Auto-updating statistics in #mymcp-dashboard
• 🗨️ Team Chat - Coordinate quests in #mymcp-game
• 🏆 Achievements - Real-time notifications for level-ups and completions
• 📈 Activity Charts - Visual progress tracking

Quick Setup

# 1. Build and configure
cd packages/slack-integration
npm install && npm run build
cp .env.example .env

# 2. Add your Slack tokens to .env
# 3. Start the integration
npm start

🌐 Multiplayer Architecture

┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│   Player A  │     │   Player B  │     │   Player C  │
│  (Engine 1) │     │  (Engine 2) │     │  (Engine 3) │
└──────┬──────┘     └──────┬──────┘     └──────┬──────┘
       │                   │                   │
       └───────────────────┴───────────────────┘
                           │
                    ┌──────▼──────┐
                    │    Redis    │
                    │   Pub/Sub   │
                    └──────┬──────┘
                           │
       ┌───────────────────┴───────────────────┐
       │                                       │
┌──────▼──────┐                         ┌──────▼──────┐
│    Slack    │                         │     MCP     │
│ Integration │                         │   Server    │
└─────────────┘                         └─────────────┘

📦 Core Components

🔧 Quick Reference

# Start services (from project root)
node tools/startup/start-engine.js      # Game engine
node tools/startup/start-mcp.js         # MCP server
node tools/startup/start-all.js         # Everything

# Development
cd packages/cli && npm run shell        # Interactive CLI
cd packages/slack-integration && npm start  # Slack bot

# Testing
node tools/testing/test-interface.js    # Test APIs
node tools/testing/test-engine-connection.js  # Check connectivity

# Setup & Configuration  
node tools/setup/setup-mcp.js          # Initial MCP setup
node tools/setup/team-setup.sh         # Team training setup

🚀 Getting Started Paths

For Individual Developers

1. Clone repo and install dependencies
2. Add LLM API key to .env
3. Start engine and CLI
4. Begin your adventure!

For Teams with Slack

1. Follow individual setup
2. Configure Slack integration
3. Create team channels
4. Share Redis connection
5. Coordinate quests together!

For Claude Desktop Users

1. Run node tools/setup/setup-mcp.js
2. Configure Claude Desktop with generated config
3. Access game directly through Claude!

📚 Documentation

• 🚀 Quick Start Guide - Get running in minutes
• 💬 Slack Setup - Team integration
• 🤖 MCP Integration - AI model setup
• 🌐 Multiplayer Guide - Distributed setup
• 📖 Full Documentation - Everything else

🧪 Testing Your Setup

# Check engine health
curl http://localhost:3000/health

# Test LLM integration
curl -X POST http://localhost:3000/api/actions/test-player \
  -H "Content-Type: application/json" \
  -d '{"type":"CHAT","payload":{"message":"Hello!"}}'

# Verify Redis connection (if using multiplayer)
redis-cli ping

🤝 Contributing

We welcome contributions! The codebase is now cleaner and more organized:

1. No more cluttered root - Tools organized in tools/ directory
2. Portable paths - No hardcoded usernames or paths
3. TypeScript throughout - Type safety everywhere
4. Clean architecture - Clear separation of concerns

See Contributing Guide for details.

🔒 Security Notes

• Never commit .env files or credentials
• Use claude_desktop_config.example.json as a template
• Redis URLs should use environment variables
• API keys should be kept private

📄 License

MIT License - see LICENSE file for details.