Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The right-hand issue is harder because it requires protocol-aware routing across aggregated MCP backends, preserving existing multi-server behavior and adding integration coverage. The left-hand issue is more localized to persistence-state reconciliation and background cost-processing logic.
}
https://github.com/berriai/litellm/issues/34906 4:3 https://github.com/berriai/litellm/issues/35131