Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Cursor Analytics (BYOK) — connector documentation

  • MCP endpoint: https://byok-cursor-analytics.connectorbay.com/mcp
  • REST API: POST https://byok-cursor-analytics.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-cursor-analytics.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Cursor Analytics Cursor team API key (admin scope), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-cursor-analytics.connectorbay.com/health · Tool schemas: https://byok-cursor-analytics.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-cursor-analytics · agent@connectorbay.com

What Cursor Analytics (BYOK) is for

Cursor Analytics (BYOK) lets an AI assistant read your own Cursor Analytics data through the Cursor Analytics API with a key you supply (Cursor team API key (admin scope)). Read-only: 11 tools (get_daily_active_users, get_agent_edits, get_tab_usage, get_model_usage, get_client_versions, get_top_file_extensions, get_mcp_adoption, get_command_adoption, get_plan_mode_adoption, get_skill_adoption, get_ask_mode_adoption). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.cursor.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Cursor Analytics. Cursor Analytics and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "How many people on my team used Cursor each day last week?"
  • "How many agent edits did my team accept this week?"
  • "What is my team's Tab acceptance rate?"
  • "Which AI models does my Cursor team use most?"
  • "Which Cursor versions is my team running?"
  • "Which file types does my team accept most AI edits for?"

What it does

  • get_daily_active_users: Get daily counts of active Cursor users, with the part that used the CLI, cloud agents and Bugbot. Team-level totals only, no per-person data. Needs an admin-scoped team API key and an Enterprise plan.
  • get_agent_edits: Get daily totals of AI-suggested edits: diffs suggested, accepted and rejected, and lines suggested and accepted. Team-level totals only, no per-person data. Needs an admin-scoped team API key and an Enterprise plan.
  • get_tab_usage: Get daily totals of Tab completions: suggestions, accepts and rejects, and lines suggested and accepted. Team-level totals only, no per-person data. Needs an admin-scoped team API key and an Enterprise plan.
  • get_model_usage: Get daily message and user counts per AI model used by the team. Team-level totals only, no per-person data. Needs an admin-scoped team API key and an Enterprise plan.
  • get_client_versions: Get daily user counts and share per Cursor client version. Team-level totals only, no per-person data. Needs an admin-scoped team API key and an Enterprise plan.
  • get_top_file_extensions: Get daily totals per file extension: files, accepts, rejects and lines suggested, accepted and rejected. Team-level totals only, no per-person data. Needs an admin-scoped team API key and an Enterprise plan.
  • get_mcp_adoption: Get daily usage counts per MCP server and tool used by the team. Team-level totals only, no per-person data. Needs an admin-scoped team API key and an Enterprise plan.
  • get_command_adoption: Get daily usage counts per slash command used by the team. Team-level totals only, no per-person data. Needs an admin-scoped team API key and an Enterprise plan.
  • get_plan_mode_adoption: Get daily Plan mode usage counts per model. Team-level totals only, no per-person data. Needs an admin-scoped team API key and an Enterprise plan.
  • get_skill_adoption: Get daily usage counts per agent skill used by the team. Team-level totals only, no per-person data. Needs an admin-scoped team API key and an Enterprise plan.
  • get_ask_mode_adoption: Get daily Ask mode usage counts per model. Team-level totals only, no per-person data. Needs an admin-scoped team API key and an Enterprise plan.

BYOK key

You bring your own Cursor Analytics Cursor team API key (admin scope) (https://cursor.com/dashboard/api). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.cursor.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Cursor Analytics API (api.cursor.com) with a BYOK key; documentation: https://cursor.com/docs/account/teams/analytics-api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Cursor Analytics. Cursor Analytics and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Cursor Analytics account.

Built for: Worldwide. Languages: English.