Within six months of launch, Atlassian's Rovo MCP server supports more than one million monthly users and over five million daily AI-driven tool interactions, signaling a shift from AI as passive software helpers to full participants in enterprise workflows.

  • Over 5 million MCP tool calls each workday and 1M+ monthly users
  • 44% of users are non-engineers, including executives and product managers
  • AI agents write data back, enhancing organizational context continuously

What happened

Atlassian released its Rovo Model Context Protocol (MCP) server less than six months ago, providing direct AI agent integration for enterprise customers. The protocol allows AI assistants such as Claude and Cursor to interface with Atlassian software comprehensively, enabling them to create, update, and link work items. Usage data shows over five million MCP tool calls take place every weekday, with more than one million monthly active users relying on the system to complete actual work tasks rather than mere demonstrations.

Significantly, 44% of these active users are outside traditional software development teams, including C-suite executives and product managers. This reflects growing adoption among knowledge workers who face complex workflows spread across multiple tools. The MCP enables AI agents to connect disparate pieces of information, tasks, and communications via the Teamwork Graph, a contextual map that unifies enterprise SaaS environments.

Why it matters

The MCP’s ability to facilitate not only AI data consumption but also AI-generated writes represents a major step forward. Nearly a third of all MCP actions involve AI creating structured data within the Atlassian ecosystem, reinforcing organizational memory and context for future interactions. This compounding effect improves overall AI performance by continuously enriching the shared knowledge base and accelerating workflows.

The tool's value is especially prominent in large enterprises where fragmented tooling and coordination challenges are more pronounced. The Teamwork Graph serves as a collective intelligence layer that bridges multiple SaaS applications like Jira, Confluence, Google Drive, and Slack. By maintaining rich, connected context, AI agents can deliver more accurate answers while reducing computational resource use, driving both efficiency and user trust.

What to watch next

Enterprises adopting the MCP framework will likely push for expanded AI integration across increasingly diverse roles and toolchains, accelerating AI participation beyond engineering into broader corporate functions. The rising user base and daily activity suggest that AI agents will become indispensable teammates with real-time commit access and sophisticated contextual awareness.

Future developments may focus on enhancing security, permissions, and auditability features to support governance needs, given the sensitive nature of AI interactions within enterprise systems. Additionally, the evolution of the Teamwork Graph and its ability to integrate more SaaS services will be critical to sustaining the growth and effectiveness of AI-powered work orchestration.

Source assisted: This briefing began from a discovered source item from Atlassian Blog. Open the original source.
How SignalDesk reports: feeds and outside sources are used for discovery. Public briefings are edited to add context, buyer relevance and attribution before they are published. Read the standards

Related briefings