Great idea, I do like the concept to give the LLM more information and context so it can decide what approach is better. But why do you implement it as a mcp server and not as a proxy to have the full context?
Great question! We initially started with a proxy, and plan to support it for users that already have things like LiteLLM setup. However we chose the MCP route, and soon plugin route, because it was much lower lift for installation. Setting up a proxy and configuring it for Cursor especially can be a bit tricky. There is actually still some code in the MCP server for a LiteLLM integration, which we hope to support officially soon.
Another large part of it is without MCP, and only a proxy in a client like cursor, the agent doesn't reason about the budget. When it has it has to use it as a tool, it actively thinks about the cost of its actions.
Another large part of it is without MCP, and only a proxy in a client like cursor, the agent doesn't reason about the budget. When it has it has to use it as a tool, it actively thinks about the cost of its actions.