IDE Integration Troubleshooting
Common issues when connecting Reeva servers to IDEs and how to fix them.
Connection Issues
Server Not Appearing
Symptoms:
- Server doesn't show in IDE's MCP panel
- No error message, just missing
Causes & Solutions:
-
Invalid JSON syntax
❌ Wrong:
{
"mcpServers": {
"reeva": {
"url": "...",
"apiKey": "...", // Trailing comma
}
}
}
✅ Correct:
{
"mcpServers": {
"reeva": {
"url": "...",
"apiKey": "..."
}
}
} -
IDE not restarted
- Close IDE completely
- Reopen (don't just reload window)
-
Config file location wrong
- Cursor: Check Settings → MCP
- Windsurf: Extensions → MCP
- Claude Code:
~/.claude/mcp-servers.json
"Failed to Connect" Error
Symptoms:
- Error message when IDE tries to connect
- Red/disconnected status indicator
Solutions:
-
Check server URL
Correct: https://api.joinreeva.com/mcp/server_abc123
Wrong: https://api.joinreeva.com/mcp/abc123
Wrong: http://api.joinreeva.com/mcp/server_abc123 (http not https) -
Verify server is active
- Log into Reeva Dashboard
- Go to Servers
- Check server shows as "Active"
- If deleted, won't connect
-
Network/firewall issues
- Check IDE can access internet
- Verify no corporate firewall blocking
- Try from different network
Authentication Issues
"Authentication Failed"
Symptoms:
- Connection works but tools fail
- Error about invalid or missing API key
Solutions:
-
Verify API key format
Correct: mcpk_1234567890abcdef
Wrong: mcpk_1234567890abcdef␣ (trailing space)
Wrong: "mcpk_1234567890abcdef" (extra quotes in config) -
Check key status
- Go to Reeva Dashboard → Servers → Your Server
- Navigate to API Keys tab
- Verify key is listed and active (not revoked)
-
Key-server mismatch
- Ensure API key is linked to the correct server
- Server-specific keys only work for one server
- Global keys must be linked to server
-
Generate new key
- If key lost or compromised
- Create new key in dashboard
- Update IDE configuration
- Restart IDE
"Unauthorized" on Tool Execution
Symptoms:
- Server connects fine
- Tool calls fail with 401/403 errors
Causes:
- API key revoked mid-session
- Permission changes on server
- Key expired (rare)
Solutions:
- Generate fresh API key
- Verify server ownership
- Check server hasn't been transferred
Tool Availability Issues
"Tool Not Found"
Symptoms:
- AI says tool doesn't exist
- Specific tool missing from available tools
Solutions:
-
Verify tool in server
- Dashboard → Servers → Your Server
- Check "Selected Tools" list
- Tool must be added to server
-
Check custom tool exists
- Dashboard → Tools → My Tools
- Verify custom tool hasn't been deleted
- Re-create if necessary
-
Clear IDE cache
- Sometimes IDE caches old tool list
- Restart IDE
- Re-fetch tool list
AI Can't See Any Tools
Symptoms:
- AI says "I don't have access to any tools"
- MCP connection shows "Connected" but tools empty
Solutions:
-
Server has no tools
- Check server in dashboard
- Must have at least one custom tool
- Add tools and restart IDE
-
MCP protocol issue
- Test server in Reeva Chat (works?)
- If Chat works but IDE doesn't: IDE issue
- Update IDE to latest version
-
Permissions issue
- Check IDE has permission to access network
- macOS: System Preferences → Security → Network
- Windows: Firewall settings
Execution Issues
"Insufficient Credits"
Symptoms:
- Tool execution starts but fails
- Error about not enough credits
Solutions:
- Check credit balance: Dashboard → Usage
- Purchase more credits
- Tool executed successfully despite error? (Check Usage logs)
Tools Execute But Fail
Symptoms:
- Tool runs but returns error
- Specific error message from external service
Debug Steps:
-
Test in Reeva Playground
- Dashboard → Servers → Your Server → Playground
- Try same tool with same parameters
- See detailed error message
-
Check credentials
- If tool requires auth (Notion, Jira, etc.)
- Dashboard → Accounts
- Verify credential is linked and active
-
Verify parameters
- Check tool's input schema
- Dashboard → Tools → [Tool Name]
- Ensure required parameters provided
Slow Tool Execution
Symptoms:
- Tools take >30 seconds
- IDE times out waiting
Expected delays:
- Web scraping: 5-30 seconds (normal)
- API calls: 1-5 seconds (normal)
- Database queries: 1-10 seconds (normal)
If consistently slow:
- Test in Playground (same speed?)
- Check network latency
- External service may be slow
- Contact support if persistent
IDE-Specific Issues
Cursor
Issue: Server added but Cursor doesn't recognize
Solution:
- Completely quit Cursor (Cmd+Q or Ctrl+Q)
- Delete config file:
~/Library/Application Support/Cursor/User/mcp-settings.json(Mac) - Restart Cursor
- Re-add configuration
- Restart again
Issue: Tools work once then stop
Solution:
- Cursor may have cached connection
- Reload window: Cmd/Ctrl+Shift+P → "Reload Window"
- Or full restart
Windsurf
Issue: Can't find MCP settings
Solution:
- Update Windsurf to latest version (MCP support added recently)
- Check Extensions marketplace for MCP plugin
- Install if not already present
Claude Code
Issue: claude mcp command not found
Solution:
# Verify installation
which claude
# If not found, reinstall
npm install -g @anthropic-ai/claude-code
# Or
pip install claude-code
# Add to PATH if needed
export PATH="$PATH:$HOME/.npm-global/bin"
Debug Checklist
When something doesn't work, verify:
- Server exists and is active in dashboard
- API key is correct (no spaces/quotes)
- Server has at least one custom tool
- Custom tools haven't been deleted
- Credits balance is sufficient
- IDE has been restarted (fully, not just reload)
- Network connection is working
- IDE is up to date
- Config JSON syntax is valid
- Tested server works in Reeva Chat
Getting Detailed Logs
Cursor
- Help → Toggle Developer Tools
- Console tab
- Look for MCP-related messages
- Filter by "MCP" or "reeva"
Windsurf
- View → Output
- Select "MCP" from dropdown
- Review connection attempts
Claude Code
# Enable debug logging
export CLAUDE_DEBUG=1
claude chat
Still Stuck?
If you've tried everything:
-
Test in isolation
- Create minimal test server with one tool
- Use in fresh IDE install
- Helps isolate problem
-
Check status page
- Verify Reeva API is operational
- No ongoing incidents
-
Contact support
- Provide:
- Server ID
- IDE and version
- Error messages
- Steps to reproduce
- We'll help debug!
- Provide: