🛡️ Rollback MCP Server

A coordinated rollback system for MCP servers that provides team safety controls and cross-platform rollback capabilities.

🚀 Features

• ✅ Cross-Platform Rollback - Coordinate rollbacks across Jira, GitHub, Slack, Confluence, Figma
• ✅ Team Safety Controls - Approval workflows and permission-based access
• ✅ Real-time Monitoring - Track all changes and rollback operations
• ✅ State Snapshots - Before/after state capture for precise rollback
• ✅ MCP Integration - Connect with other MCP servers seamlessly
• ✅ Free Tier Deployment - Deploy on Supabase + Vercel for free

📋 Prerequisites

• Node.js 18+
• Supabase account (free tier)
• Vercel account (free tier)
• MCP server connections (Jira, GitHub, etc.)

🛠️ Setup

1. Clone and Install

1git clone <your-repo>
2cd rollback-server
3npm install

2. Supabase Setup

1. Create Supabase Project

   • Go to supabase.com
   • Create new project
   • Get your project URL and anon key

2. Run Database Schema

   • Go to SQL Editor in Supabase
   • Copy and run supabase-schema.sql

3. Environment Variables

   1cp .env.example .env

   Add your Supabase credentials:

   1SUPABASE_URL=your_supabase_url
   2SUPABASE_ANON_KEY=your_supabase_anon_key

3. Local Development

1# Start development server
2npm run dev
3
4# Build for production
5npm run build
6npm start

4. Deploy to Vercel

1# Install Vercel CLI
2npm i -g vercel
3
4# Deploy
5vercel --prod

🔧 Configuration

MCP Server Connections

Connect to your existing MCP servers:

1{
2  "mcpServers": {
3    "rollback-server": {
4      "command": "node",
5      "args": ["dist/index.js"],
6      "env": {
7        "SUPABASE_URL": "your_supabase_url",
8        "SUPABASE_ANON_KEY": "your_supabase_anon_key"
9      }
10    }
11  }
12}

Platform API Keys

Add your platform API keys to environment variables:

1# Jira
2JIRA_URL=https://your-domain.atlassian.net
3JIRA_USERNAME=your_email
4JIRA_API_TOKEN=your_api_token
5
6# GitHub
7GITHUB_TOKEN=your_github_token
8
9# Slack
10SLACK_BOT_TOKEN=your_slack_bot_token
11
12# Confluence
13CONFLUENCE_URL=https://your-domain.atlassian.net
14CONFLUENCE_USERNAME=your_email
15CONFLUENCE_API_TOKEN=your_api_token
16
17# Figma
18FIGMA_TOKEN=your_figma_token

🎯 Usage

Register a Rollback Task

1// When a change is made, register it for potential rollback
2await rollbackServer.register_rollback({
3  taskId: "task_123",
4  platform: "jira",
5  operation: "update",
6  agentId: "agent_456",
7  beforeState: {
8    id: "state_789",
9    timestamp: "2024-01-01T00:00:00Z",
10    data: {
11      issueKey: "PROJ-123",
12      fields: { summary: "Old Summary" }
13    }
14  }
15});

Execute Rollback

1// Execute rollback with approval
2await rollbackServer.execute_rollback({
3  rollbackId: "rollback_123",
4  approverId: "user_456",
5  force: false
6});

Approve Rollback

1// Approve or reject a rollback
2await rollbackServer.approve_rollback({
3  rollbackId: "rollback_123",
4  approverId: "user_456",
5  approved: true,
6  comment: "Looks good to rollback"
7});

🔗 Integration Examples

With Your Enhanced Orchestrator

1// In your orchestrator, add rollback registration
2import { RollbackMCPServer } from './rollback-server';
3
4const rollbackServer = new RollbackMCPServer();
5
6// After each task execution
7await rollbackServer.register_rollback({
8  taskId: task.id,
9  platform: task.platform,
10  operation: task.operation,
11  agentId: task.agentId,
12  beforeState: task.beforeState
13});

With Jira MCP Server

1{
2  "mcpServers": {
3    "jira": {
4      "command": "mcp-jira-server",
5      "args": ["--config", "jira-config.json"]
6    },
7    "rollback": {
8      "command": "node",
9      "args": ["dist/index.js"]
10    }
11  }
12}

📊 Monitoring

Real-time Dashboard

Access your rollback dashboard at:

https://your-vercel-app.vercel.app

API Endpoints

• GET /api/rollbacks - List rollback tasks
• POST /api/rollbacks - Register new rollback
• PUT /api/rollbacks/:id/approve - Approve rollback
• POST /api/rollbacks/:id/execute - Execute rollback

🛡️ Safety Features

Approval Workflows

1. Automatic Registration - All changes are registered
2. Manual Approval - Requires team member approval
3. Force Rollback - Emergency rollback option
4. Audit Trail - Complete history of all actions

Team Roles

• Admin - Full access to all features
• Approver - Can approve/reject rollbacks
• Viewer - Read-only access

🚨 Emergency Procedures

Immediate Rollback

1// Force rollback without approval
2await rollbackServer.execute_rollback({
3  rollbackId: "rollback_123",
4  approverId: "emergency_user",
5  force: true
6});

Bulk Rollback

1// Rollback all recent changes by an agent
2const tasks = await rollbackServer.list_rollbacks({
3  agentId: "problematic_agent",
4  status: "completed"
5});
6
7for (const task of tasks) {
8  await rollbackServer.execute_rollback({
9    rollbackId: task.id,
10    approverId: "admin",
11    force: true
12  });
13}

📈 Free Tier Limits

Supabase (Free)

• ✅ 500MB database storage
• ✅ 50,000 API calls/month
• ✅ Unlimited real-time subscriptions
• ✅ 50,000 users

Vercel (Free)

• ✅ 100GB bandwidth/month
• ✅ 100GB-hours serverless functions
• ✅ Unlimited deployments

Perfect for small teams (2-5 people)!

🔧 Troubleshooting

Common Issues

1. Connection Failed

   • Check your Supabase credentials
   • Verify environment variables

2. Rollback Failed

   • Check platform API keys
   • Verify before state data

3. Approval Required

   • Ensure user has approver role
   • Check team member permissions

Debug Mode

1# Enable debug logging
2DEBUG=rollback:* npm run dev

🤝 Contributing

1. Fork the repository
2. Create feature branch
3. Make changes
4. Test thoroughly
5. Submit pull request

📄 License

MIT License - see LICENSE file for details

🆘 Support

• Issues: GitHub Issues
• Discussions: GitHub Discussions
• Documentation: Wiki

---

Built with ❤️ for team safety and coordinated rollback operations