Description:

Currently there is no way to visualize or analyze usage metrics for the Atlassian Rovo MCP Server beyond manually exporting and parsing audit logs. I'd like to request the creation of native dashboards and/or reporting tools that surface MCP usage data directly within Atlassian Administration.

Problem Statement:

When the Atlassian Rovo MCP Server is enabled on Jira and Confluence, administrators have very limited visibility into how it's being used:

•  The only available data is in the Audit Log, which requires manual filtering or export to derive any meaningful insights.
•  There is no dashboard showing usage trends, active users, or tool invocation volumes.
•  Tool-level breakdowns (e.g., which MCP tools are called most frequently) are not available at all.

This creates a significant blind spot for administrators who need to understand adoption, troubleshoot issues, or demonstrate the value of MCP integrations to their organization.

Proposed Solution:

Atlassian should introduce a dedicated MCP Usage Analytics section within Atlassian Administration, including:

 1.  Usage volume dashboard: Total MCP tool invocations over time (daily/weekly/monthly), per user and per connected AI client (e.g., Claude, Cursor, VS Code).
 2.  Tool-level breakdown: Which MCP tools are being invoked most frequently (e.g., search issues, create page, summarize content).
 3.  Connected clients overview: Which OAuth-authorized clients/apps are actively using the MCP server and how often.
 4.  Error & failure tracking: Failed tool invocations, authentication errors, and connectivity issues surfaced in a readable format.
 5.  User activity summary: Which users are actively using MCP-connected AI tools, to help with license planning and adoption tracking.

Why this matters:

•  Helps admins understand and demonstrate ROI of MCP/AI integrations.
•  Enables proactive troubleshooting of failing tools or unauthorized access.
•  Reduces reliance on manual audit log exports and external BI tooling.
•  Supports enterprise governance and compliance requirements.