I Built a Cursor Plugin to Track My Team's AI Spend From the IDE

I manage a Cursor Enterprise team with 50+ developers. AI spend has become the new cloud cost problem, except there's no Datadog for it. You find out about cost spikes when the invoice lands, weeks after the damage is done. Cursor has an admin dashboard, but it shows raw numbers. It doesn't answer questions like "why did our spend jump 40% last Tuesday?" or "who switched to Opus and tripled their daily cost?" So I built a Cursor plugin that wraps the Cursor Enterprise API as MCP tools, so my AI agent can answer those questions for me, right in the IDE. A Cursor MCP server for enterprise usage and spending data cursor-usage is a Cursor plugin (also works with Claude Code) that exposes the full Cursor Enterprise Admin and Analytics APIs through the Model Context Protocol (MCP). If you're not familiar with MCP, it's the standard that lets AI agents call external tools. In this case, the "tools" are your team's spending and usage data. You install the plugin, set your API key, and start as