FIND_MCP_ERRORS.md•2.13 kB
# How to Find MCP Errors in Cursor
## The Problem
You're seeing errors, but they're NOT MCP-related. We need to find the actual MCP connection errors.
## Current Errors (Can Ignore)
- ✅ `punycode` deprecation = Node.js warning (ignore)
- ✅ `ConnectError: unauthenticated` = Cursor team features (ignore)
- ✅ `OTLPExporterError` = Telemetry (ignore)
## How to Find MCP Errors
### Method 1: Clear Console and Restart
1. **Clear Console**: Click trash icon in Developer Console
2. **Close Cursor completely** (all windows)
3. **Restart Cursor**
4. **Immediately check Console** (before doing anything else)
5. **Search for**: `mcp`, `server`, `code-intelligence`
### Method 2: Filter Console
In Developer Console:
1. Click the **filter icon** (funnel)
2. Type: `mcp` or `error`
3. Look for red messages
### Method 3: Check MCP Status (if available)
Some Cursor versions show MCP server status:
- Look in status bar (bottom of Cursor)
- Check Settings → Extensions → MCP
- Look for "MCP" or "Servers" in settings
### Method 4: Check Output Panel
1. View → Output
2. Select "MCP" or "Extension Host" from dropdown
3. Look for errors
## What MCP Errors Look Like
### Error 1: Server Not Starting
```
Failed to start MCP server: code-intelligence
Error: spawn python.exe ENOENT
```
### Error 2: Path Not Found
```
Cannot find module: C:\AIStack-MCP\mcp_intelligence_server.py
```
### Error 3: Import Error
```
ModuleNotFoundError: No module named 'fastmcp'
```
### Error 4: Workspace Error
```
Workspace does not exist: C:\AIStack
```
## If No Errors Appear
If you see **NO MCP errors** in console, it means:
- Cursor might not be trying to start the server
- Server might be starting but failing silently
- Configuration might not be loaded
**Next step**: Check if the server process appears after restart:
```powershell
Get-Process | Where-Object { $_.CommandLine -like "*mcp_intelligence*" }
```
## What to Do
1. **Clear console and restart Cursor**
2. **Immediately check console** for MCP errors
3. **If no errors**: Server might not be starting at all
4. **Copy any MCP-related errors** you find