Troubleshooting

Frequently Faced Issues and Solutions

Encountering challenges with CodeGlide? This comprehensive guide addresses the most frequently reported issues and provides step-by-step solutions to get you back on track quickly.

MCP Generation Failed

If MCP generation fails, ensure your repository contains recognizable API patterns. Check that your code follows standard conventions for your chosen framework.

Common Causes:

• Repository doesn't contain API endpoints
• Code doesn't follow standard framework patterns
• Missing or incomplete API documentation
• Repository structure is too complex or nested

Solutions:

• Verify your repository contains REST API endpoints
• Ensure code follows standard conventions (Express.js, FastAPI, etc.)
• Add OpenAPI/Swagger documentation if available
• Try analyzing a simpler branch or subdirectory

Authentication Errors

Verify that CodeGlide has the necessary permissions and that your GitHub token hasn't expired. Re-authenticate if needed.

Common Causes:

• GitHub token has expired
• Insufficient repository permissions
• Repository access has been revoked
• Two-factor authentication issues

Solutions:

• Re-authenticate with GitHub
• Ensure admin access to the repository
• Check repository visibility settings
• Verify 2FA is properly configured

Analysis Timeout

Large repositories may take longer to analyze. Consider analyzing specific branches or subdirectories containing your API code.

Common Causes:

• Repository is very large (>1GB)
• Many dependencies and submodules
• Complex nested directory structures
• Network connectivity issues

Solutions:

• Analyze specific branches instead of main
• Focus on API-specific directories
• Remove unnecessary files before analysis
• Check your internet connection