-
-
Notifications
You must be signed in to change notification settings - Fork 34
MCP Overview
Saros Industries edited this page Jun 28, 2025
·
1 revision
CursorRIPERβ¦Ξ£ supports optional integration with MCP services, extending the framework's capabilities with external tools while maintaining its core efficiency.
Model Context Protocol (MCP) is a standard for connecting AI assistants to external services. It enables:
- π§ Tool integration without custom code
- π Secure service connections
- π Extended capabilities
- π Consistent interfaces
| Service | Symbol | Purpose | Commands |
|---|---|---|---|
| GitHub | Ξ | Repository management |
!gr, !gp, !gpr
|
| Web Search | Ξ | Research capabilities |
!ws, !wl, !wf
|
| Browser | Ξ₯ | Automation & testing |
!pn, !ps, !pt
|
| Docker | Ξ | Container management |
!dc, !dd, !dl
|
- Filesystem (Built-in) - Advanced file operations
- SQLite - Database operations
- Fetch - URL content retrieval
- Memory - Knowledge graph
βββββββββββββββββββββββββββββββββββββββ
β CursorRIPERβ¦Ξ£ Framework β
βββββββββββββββββββββββββββββββββββββββ€
β Core Framework (Always Active) β
β βββ RIPER Modes (Ξ©) β
β βββ Memory System (Ξ£) β
β βββ Protection (Ξ¨) β
β βββ Permissions (β) β
βββββββββββββββββββββββββββββββββββββββ€
β MCP Layer (Optional) β
β βββ GitHub Service (Ξ) β
β βββ Web Search (Ξ) β
β βββ Browser Automation (Ξ₯) β
β βββ Docker Service (Ξ) β
βββββββββββββββββββββββββββββββββββββββ
# GitHub Integration
npm install -g @modelcontextprotocol/server-github
export GITHUB_TOKEN=your_token
# Web Search
npm install -g @modelcontextprotocol/server-brave-search
export BRAVE_SEARCH_API_KEY=your_key
# Browser Automation
npm install -g @executeautomation/playwright-mcp-server
# Docker
npm install -g docker-mcpUpdate .cursor/mcp.json:
{
"mcpServers": {
"github": {
"command": "mcp-server-github",
"env": {
"GITHUB_TOKEN": "${env:GITHUB_TOKEN}"
}
},
"brave-search": {
"command": "mcp-server-brave-search",
"env": {
"BRAVE_SEARCH_API_KEY": "${env:BRAVE_SEARCH_API_KEY}"
}
}
}
}Uncomment service sections in your framework rules.
| Service | Research | Innovate | Plan | Execute | Review |
|---|---|---|---|---|---|
| GitHub Read | β | β | β | β | β |
| GitHub Write | β | β | β | β | β |
| Web Search | β | β | β | β | β |
| Browser Read | β | β | β | β | β |
| Browser Write | β | β | β | β | β |
| Docker Read | β | β | β | β | β |
| Docker Write | β | β | β | β | β |
- No search in EXECUTE: Maintains implementation focus
- Write operations limited: Prevents accidental modifications
- Read always allowed: Information gathering is safe
/research
!ws "latest authentication best practices"
!gr "oauth2 implementation examples"
/execute
!pn https://localhost:3000
!ps login-page
!pt # Start test recording
/execute
!gp # Push completed feature
!gpr # Create pull request
/execute
!dc nodejs:18 # Create dev container
!dl my-app # Check logs
- Framework works perfectly without MCP
- Enable only services you need
- Start with core framework first
- Services respect mode permissions
- Some operations blocked by mode
- Plan service usage appropriately
- Store API keys securely
- Use environment variables
- Never commit credentials
- Master core framework
- Add one service at a time
- Learn service-specific commands
- Integrate into workflow
β = {
Ξ: { // GitHub
1: {op: "search_repositories", h: "!gr"},
2: {op: "create_repository", h: "!gc"},
3: {op: "push_files", h: "!gp"},
4: {op: "create_pull_request", h: "!gpr"}
},
Ξ: { // Web Search
1: {op: "web_search", h: "!ws"},
2: {op: "local_search", h: "!wl"},
3: {op: "fetch_url", h: "!wf"}
},
Ξ₯: { // Browser
1: {op: "navigate", h: "!pn"},
2: {op: "screenshot", h: "!ps"},
3: {op: "test_record", h: "!pt"}
},
Ξ: { // Docker
1: {op: "create_container", h: "!dc"},
2: {op: "deploy_compose", h: "!dd"},
3: {op: "get_logs", h: "!dl"}
}
}Error: MCP service 'github' not found
Solution: Install service and restart Cursor
β οΈ GitHub write operations not allowed in RESEARCH mode
Solution: Switch to EXECUTE mode
Error: GITHUB_TOKEN not set
Solution: Export environment variable
β οΈ Web search blocked in EXECUTE mode
Solution: Complete task, then switch modes
"Show available MCP services"
"Test GitHub connection"
"Verify web search API"
!mcp-status # Check all services
!mcp-test github # Test specific service
!mcp-reload # Reload services
/research
!ws "microservices patterns" # Web search
!gr "microservice examples" # GitHub search
!wf "https://patterns.dev" # Fetch specific page
/execute
!gc my-new-project # Create repo
# ... develop feature ...
!gp # Push changes
!gpr # Create PR
/execute
!pn http://localhost:3000 # Navigate
!ps before-change # Screenshot
# ... make changes ...
!ps after-change # Screenshot
!pt # Record test
- Master RIPER modes
- Learn memory system
- Understand protections
- Enable GitHub or Web Search
- Learn basic commands
- Integrate into workflow
- Add browser automation
- Combine services
- Create workflows
- Custom integrations
- Service combinations
- Team workflows
Ready to integrate specific services?
- GitHub Integration - Repository management
- Web Search - Research capabilities
- Browser Automation - Testing tools
- Docker Integration - Container management
- ποΈ Framework Overview
- π RIPER Modes
- πΎ Memory System
- π£ Symbolic Notation
- π Phase Management
- π‘οΈ Code Protection
- π Context References
- π Permission System
- π Cross-References
- πΎ Backup System
- π Mode Transitions
- πΎ Memory Management
- π‘οΈ Protection Workflow
- π Context Management
- π₯ Team Collaboration
- π£ Symbol Reference
- β¨οΈ Command Reference
- π Mode Reference
- π Permission Matrix
- π API Reference
- π Overview
- π GitHub Integration
- π Web Search
- π Browser Automation
- π³ Docker Integration
-
Installation Issues
- Node.js Version Compatibility
- Package Installation Failures
- Framework Dependencies Missing
- Database Connection Issues
- Port Conflicts
- Environment Setup Issues
- Build and Development Issues
- Framework CLI Issues
-
Configuration & Runtime Issues
- Framework Configuration Problems
- Runtime Performance Issues
- Module Loading and Plugin Issues
- Database and Storage Issues
- Memory Leaks and High Memory Usage
- High CPU Usage
-
BMAD Module Issues
- BMAD Module Initialization Problems
- Business Model Canvas Issues
- Stakeholder Management Issues
- Analytics and Reporting Issues
- Performance Optimization
-
Database & API Issues
- Database Connection Problems
- Database Migration Issues
- API Performance and Reliability Issues
- Data Consistency Issues
- Transaction Problems
-
Performance & Memory Issues
- Memory Management
- CPU Optimization
- Database Query Performance
- Caching Issues
- Resource Monitoring
-
Security & Authentication Issues
- Authentication Failures
- Authorization Problems
- JWT Token Issues
- Session Management
- CORS and Security Headers
- SSL/TLS Configuration
-
Deployment & Production Issues
- Production Deployment Failures
- Environment Configuration
- Load Balancing Issues
- Monitoring and Logging
- Backup and Recovery
When reporting issues, please include:
- Framework version (
npm list @cursoriper/core) - Node.js version (
node --version) - Operating system and version
- Error messages and stack traces
- Steps to reproduce the issue
- Configuration files (sanitized)
- Recent changes or deployments
- Technical Support: support@cursoriper.com
- Documentation: https://docs.cursoriper.com
- Community Forum: https://community.cursoriper.com