[codex] Add an evolve-mcp launcher with SSE support#175
Conversation
|
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 19 minutes and 44 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 (4)
✨ 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 |
dca7cd2 to
bddaaa0
Compare
Summary
This PR adds a dedicated
evolve-mcpconsole script for launching the MCP server and extends the launcher so it can run over eitherstdioorsse.What Changed
evolve-mcp = "altk_evolve.frontend.mcp.__main__:main"inpyproject.toml--transport,--host, and--portstdiossemode directly throughmcp.run(...)without starting the UI threadWhy
The previous docs pointed at module or
fastmcpinvocations directly. This change provides a single supported entrypoint for local usage and MCP client configuration, while also making SSE launch behavior available from the same command.Impact
uv run evolve-mcpuv run evolve-mcp --transport sse --port 8201Validation
uv run pytest -v tests/unit/test_mcp_launcher.py