Overview
Connect CodeAlive with Cursor IDE to enhance your AI-powered development experience. CodeAlive provides Cursor with deep contextual understanding of your entire codebase through the Model Context Protocol (MCP).Prerequisites
- Cursor installed
- CodeAlive account with API key (Sign up here)
- Indexed repositories in your CodeAlive dashboard
Connecting to CodeAlive
Open Cursor Settings
Navigate to Cursor’s MCP settings:
- macOS: Cmd+Shift+P → “MCP: Configure Servers”
- Windows/Linux: Ctrl+Shift+P → “MCP: Configure Servers”
- Or navigate through: Settings → Features → MCP
Add CodeAlive Server
Cursor supports MCP with elicitation and resources:Option 1: Project-specific (Option 2: Global (
.cursor/mcp.json):~/.cursor/mcp.json):Cursor’s Composer Agent automatically uses MCP tools when relevant
Reload Cursor
Reload the Cursor window for changes to take effect:
- All platforms: Cmd/Ctrl+R or “Developer: Reload Window”
Cursor Rules Configuration
Create a.cursorrules file in your project root to optimize Cursor’s AI with CodeAlive:
Usage Patterns
- Smart Completion
- Intelligent Refactoring
- Context-Aware Debugging
Advanced Features
Multi-File Operations
Cursor can use CodeAlive to work across multiple files:Find Dependencies
Find Dependencies
Impact Analysis
Impact Analysis
Pattern Matching
Pattern Matching
Workspace Configuration
Project-Specific Settings
Create.cursor/settings.json in your project:
Team Collaboration
Share configuration with your team:- Add to version control (without API keys)
- Team members set environment variable:
Docker Alternative
Run CodeAlive locally with Docker:Productivity Tips
Quick Commands
Create custom Cursor commands for CodeAlive operations
Context Windows
Use CodeAlive for codebases exceeding context limits
Model Selection
Use GPT-4 for complex analysis, GPT-3.5 for quick searches
Team Standards
Document conventions in .cursorrules
Troubleshooting
CodeAlive not responding
CodeAlive not responding
Solutions:
- Check MCP server status in Cursor console
- Verify API key is correct and active
- Reload Cursor window (Cmd/Ctrl+R)
- Check network connectivity
Incomplete code context
Incomplete code context
Solutions:
- Ensure repositories are fully indexed
- Wait for indexing to complete
- Verify API key has repository access
- Check specific repository filters
Slow responses
Slow responses
Solutions:
- Use more specific queries
- Limit search to specific repositories
- Check indexing status in dashboard
- Consider Docker deployment