Bishop MCP (Master Control Program)
by mbishopfx
This is an advanced MCP Server script I have developed and would like to share.
What is Bishop MCP (Master Control Program)
Bishop MCP (Master Control Program)
An advanced, enterprise-grade Master Control Program for efficient app building, deployment, and management in Cursor IDE. This system provides a comprehensive suite of tools for managing your development workflow, from build automation to deployment orchestration.
๐ Features
Core Functionality
-
Advanced Build System
- Concurrent build management
- Build artifact caching
- Version control integration
- Build logs and metrics
- Artifact retention policies
-
Deployment Orchestration
- Multi-environment support (Dev/Staging/Prod)
- Zero-downtime deployments
- Automatic rollback capabilities
- Health check monitoring
- Deployment configuration management
-
User Management
- Role-based access control (RBAC)
- JWT authentication
- Session management
- User activity tracking
Advanced Features
Real-time Monitoring
- WebSocket-based real-time updates
- Build and deployment progress tracking
- System metrics visualization
- Resource usage monitoring
- Custom alert configurations
Security
- Rate limiting protection
- HTTPS support
- CORS configuration
- JWT-based authentication
- Role-based access control
- Security headers with Helmet
Logging and Analytics
- Structured JSON logging
- Log rotation
- Audit trails
- Performance metrics
- Error tracking and reporting
Integration Capabilities
- Docker container support
- Git repository integration
- CI/CD pipeline hooks
- Webhook support
- Email notifications
- Redis caching
Monitoring and Metrics
- Prometheus integration
- Grafana dashboards
- Health check endpoints
- Performance monitoring
- Resource usage tracking
๐ Getting Started
Prerequisites
- Node.js (v18 or higher)
- PostgreSQL (v13 or higher)
- Redis (v6 or higher)
- Docker (optional)
Installation
- Clone the repository:
git clone https://github.com/your-username/bishop-mcp.git
cd bishop-mcp
- Install dependencies:
npm install
- Set up environment variables:
cp .env.example .env
# Edit .env with your configuration
- Set up the database:
# Start PostgreSQL
npm run migrate:up
npm run seed
- Start the server:
# Development
npm run dev
# Production
npm run build
npm start
Docker Deployment
- Build the Docker image:
npm run docker:build
- Run the container:
npm run docker:run
๐ API Documentation
Authentication
- POST /api/auth/login
- POST /api/auth/register
- POST /api/auth/refresh-token
- POST /api/auth/logout
Apps
- GET /api/apps
- GET /api/apps/:id
- POST /api/apps
- PUT /api/apps/:id
- DELETE /api/apps/:id
Builds
- POST /api/apps/:id/build
- GET /api/apps/:id/builds
- GET /api/apps/:id/builds/:buildId
- DELETE /api/apps/:id/builds/:buildId
- GET /api/apps/:id/builds/:buildId/status
- GET /api/apps/:id/builds/:buildId/logs
- GET /api/apps/:id/builds/:buildId/artifacts
Deployments
- POST /api/apps/:id/deploy
- GET /api/apps/:id/deployments
- GET /api/apps/:id/deployments/:deploymentId
- POST /api/apps/:id/deployments/:deploymentId/rollback
- DELETE /api/apps/:id/deployments/:deploymentId
- GET /api/apps/:id/deployments/:deploymentId/status
- GET /api/apps/:id/deployments/:deploymentId/logs
Environments
- GET /api/environments
- POST /api/environments
- PUT /api/environments/:id
- DELETE /api/environments/:id
๐ง Configuration
Environment Variables
-
Server Configuration
- PORT: Server port (default: 3000)
- NODE_ENV: Environment mode
- DATABASE_URL: PostgreSQL connection string
-
Security
- JWT_SECRET: JWT signing key
- JWT_EXPIRES_IN: Token expiration
- RATE_LIMIT_WINDOW: Rate limiting window
- RATE_LIMIT_MAX_REQUESTS: Maximum requests per window
-
Build System
- BUILD_TIMEOUT: Maximum build duration
- MAX_CONCURRENT_BUILDS: Concurrent build limit
- BUILD_CACHE_TTL: Cache retention period
- BUILD_ARTIFACT_RETENTION_DAYS: Artifact retention period
-
Deployment
- DEPLOYMENT_TIMEOUT: Maximum deployment duration
- MAX_CONCURRENT_DEPLOYMENTS: Concurrent deployment limit
- DEPLOYMENT_ROLLBACK_ENABLED: Enable automatic rollbacks
- DEPLOYMENT_HEALTH_CHECK_TIMEOUT: Health check timeout
๐ Monitoring
Metrics
Access metrics dashboard:
http://localhost:9090/metrics
Grafana Integration
- Configure Grafana datasource with Prometheus
- Import provided dashboards from
/grafana/dashboards
๐ Security
Authentication
- JWT-based authentication
- Role-based access control
- Rate limiting protection
- CORS configuration
SSL/TLS
Enable HTTPS in production:
- Set ENABLE_HTTPS=true in .env
- Provide SSL certificate paths:
- SSL_CERT_PATH
- SSL_KEY_PATH
๐ค Contributing
- Fork the repository
- Create your feature branch
- Commit your changes
- Push to the branch
- Create a Pull Request
๐ License
This project is licensed under the MIT License - see the LICENSE file for details.
๐ Acknowledgments
- Built with TypeScript and Node.js
- Powered by Express.js
- Database by PostgreSQL
- Caching by Redis
- Containerization by Docker
- Monitoring by Prometheus & Grafana
Leave a Comment
Comments section will be available soon. Stay tuned!
Frequently Asked Questions
What is MCP?
MCP (Model Context Protocol) is an open protocol that standardizes how applications provide context to LLMs. Think of MCP like a USB-C port for AI applications, providing a standardized way to connect AI models to different data sources and tools.
What are MCP Servers?
MCP Servers are lightweight programs that expose specific capabilities through the standardized Model Context Protocol. They act as bridges between LLMs like Claude and various data sources or services, allowing secure access to files, databases, APIs, and other resources.
How do MCP Servers work?
MCP Servers follow a client-server architecture where a host application (like Claude Desktop) connects to multiple servers. Each server provides specific functionality through standardized endpoints and protocols, enabling Claude to access data and perform actions through the standardized protocol.
Are MCP Servers secure?
Yes, MCP Servers are designed with security in mind. They run locally with explicit configuration and permissions, require user approval for actions, and include built-in security features to prevent unauthorized access and ensure data privacy.
Related MCP Servers
Fetch
Web content fetching and conversion for efficient LLM usage
Playwright
A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. This server enables LLMs to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or visually-tuned models.
puppeteer-mcp-server
Puppeteer
Browser automation and web scraping
Playwright Universal MCP
A universal Playwright MCP server for browser automation in containerized environments
MCP Server Playwright
MCP Server Playwright - A browser automation service for Claude Desktop
OneNote MCP Server
MCP server for browsing and interacting with OneNote web app using browser-use automation
Playwright
๐ Fetcher MCP - Playwright Headless Browser Server
MCP server for fetch web page content using Playwright headless browser.
MCP Browser
NeoForge Browser MCP server - used to test the frontend
Submit Your MCP Server
Share your MCP server with the community
Submit Now