refactor: improve MCP configuration handling and documentation#26
Conversation
- Updated the `resolve_mcp_config_path` function to simplify the logic for determining the `mcp.json` path, ensuring consistent behavior for both debug and release builds. - Enhanced error handling in the `handle_mcp_filesystem_put` function to utilize the loaded catalog for syncing mounted tools. - Revised documentation in `custom-mcp-tools.md` to clarify the local development path for `mcp.json`. - Updated the tool catalog version in `tools.json` to reflect recent changes.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 50 minutes and 22 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
resolve_mcp_config_pathfunction to simplify the logic for determining themcp.jsonpath, ensuring consistent behavior for both debug and release builds.handle_mcp_filesystem_putfunction to utilize the loaded catalog for syncing mounted tools.custom-mcp-tools.mdto clarify the local development path formcp.json.tools.jsonto reflect recent changes.