A
licenseA
qualityB
maintenanceMCP server exposing Cursor's HTTP APIs for managing Cloud Agents, Team/Org Admin, Analytics, Bugbot, AI Code Tracking, and Fleet with read-only and read-write modes.
61
MIT
cursor-usage
by ofershap
Related Servers
Alternatives to cursor-usage
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceAn MCP server that provides AI assistants with team analytics capabilities for Cursor editor, allowing them to retrieve team member information, usage metrics, and spending data through natural language queries.33MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that instruments Cursor AI agent interactions with OpenTelemetry traces and logs to monitor agent turns and performance. It enables tracking of user queries, assistant responses, and tool usage through GenAI-compliant telemetry spans.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that captures and exposes usage, cost, productivity, and activity metrics for local-first software engineering teams, including LLM token usage, cloud cost savings, and developer activity tracking.-
- AlicenseAqualityBmaintenanceA FastMCP server for Cursor platform APIs enabling spend guardrails, cloud agent monitoring, and inter-agent inbox messaging.61MIT
- AlicenseAqualityDmaintenanceMCP server for querying OpenAI usage and cost data, including spend summaries, daily breakdowns, month-over-month comparisons, and token usage by model.3MIT
TDQS
A3.6/5.0
Scored across 17 tools
Disambiguation4/5
Most tools have distinct purposes (e.g., get_agent_edits vs get_tabs vs get_model_usage). However, get_daily_usage and get_usage_events may overlap slightly, and get_spending/get_billing_groups both deal with costs, but descriptions clarify differences.
Naming Consistency5/5
All tools follow a consistent get_noun pattern in snake_case (e.g., get_daily_usage, get_team_members). The only outlier is set_spend_limit which uses 'set', which is appropriate for a mutation.
Tool Count4/5
17 tools is slightly high but well-justified for a comprehensive analytics server. Each tool covers a distinct metric, and the count is within reasonable bounds.
Completeness4/5
Covers most key areas: user activity, model usage, spending, team members, and even includes a mutation (set_spend_limit). However, lacks tools for inviting/removing team members or managing billing settings.
Maintenance
ActivityInactive
ResponsivenessNo issues