get_conversation_analytics
Analyze Cursor chat data to uncover coding patterns, file activity, and language usage trends. Use project-specific insights for focused development analysis or explore detailed conversation breakdowns for follow-up actions.
Instructions
Get comprehensive analytics and statistics about Cursor chats including usage patterns, file activity, programming language distribution, and temporal trends. BEST PRACTICE: Use projectPath parameter for project-specific analytics - this analyzes only conversations that worked on files in that project, providing much more relevant insights for understanding coding patterns, file usage, and development activity within a specific codebase. WORKFLOW TIP: Always include "files" and "languages" in breakdowns - these contain conversation IDs in their arrays that you can immediately use with get_conversation tool. Use includeConversationDetails=true when you need the full conversation ID list and basic metadata for follow-up analysis.
Input Schema
Name | Required | Description | Default |
---|---|---|---|
includeBreakdowns | No | Types of breakdowns to include in the analysis. IMPORTANT: "files" and "languages" breakdowns contain conversation IDs in their arrays - use these for follow-up analysis! | |
includeConversationDetails | No | Include full conversation ID list and basic metadata (increases response size significantly) | |
outputMode | No | Output format: "json" for formatted JSON (default), "compact-json" for minified JSON | json |
projectPath | No | **HIGHLY RECOMMENDED** Project/codebase name (e.g., "my-app") or full path for project-scoped analysis. When provided, analyzes only conversations that worked on files in that project, giving much more relevant insights about coding patterns and development activity. | |
recentDays | No | Number of recent days to analyze (1-365) | |
scope | No | Analysis scope: all conversations, recent only, or project-specific. Use "project" with projectPath for focused project analysis. | all |