Cursor Admin MCP Server
Related Servers
Alternatives to Cursor Admin MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that wraps Cursor Enterprise API to enable AI agents to answer questions about team spending, usage, and model adoption.1723 npm2MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that provides product and web analytics capabilities, allowing AI coding assistants to query funnels, retention, trends, feature flags, A/B tests, and more in natural language.3MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides detailed information about your development environment to the Cursor code editor, enabling more context-aware assistance.7MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables AI agents to query RevenueCat's subscription analytics API using natural language, retrieving metrics like MRR, churn, and revenue.35 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables SQL analytics on DuckDB and MotherDuck databases, allowing AI assistants and IDEs to query and analyze data.MIT
- AlicenseBqualityCmaintenanceAn MCP server for unified cost tracking and analysis across AWS, OpenAI, and Anthropic. It enables users to query expenditures, compare costs across providers, and analyze usage trends through natural language.10MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_daily_usage_data focuses on usage metrics, get_spending_data on financial data, and get_team_members on personnel information. There is no overlap in functionality or ambiguity between them.
All tool names follow a consistent verb_noun pattern with 'get_' as the prefix, followed by a descriptive noun phrase (e.g., daily_usage_data, spending_data, team_members). This uniformity makes the tools predictable and easy to understand.
With only 3 tools, the set feels thin for an admin server, as it lacks operations like update, create, or delete for team members or spending. While the tools cover key read-only functions, the scope suggests more administrative actions would be expected.
The toolset is severely incomplete for an admin domain, offering only read operations (get) without any ability to modify data, manage users, or handle configurations. This creates significant gaps that will limit agent effectiveness in administrative tasks.