That is the pitch. The more interesting parts sit underneath it: a rebuilt Model Context Protocol server, live presence indicators for agents, and a token-efficiency figure Atlassian puts at up to 25% for Jira and Confluence tasks. Atlassian documents the protocol on its own AMP product page, and the Team '26 Europe announcements were issued in the company's release of 7 October 2026.
What AMP adds to a Jira board
An agent under AMP is not a shared service account. It gets its own identity, a defined scope of authority, access to shared context from Atlassian's Teamwork Graph, and a record of what it changed. Atlassian describes the shift as moving from single-player prompting to multiplayer teamwork, which is marketing language for something concrete: the agent's actions become visible objects in the same system your employees already work in.
Live agent presence is the visible half. Real-time cursors, presence bars and session tracking on Jira boards mean a human can see which agent is touching which issue while it is doing it, and stop it. The other half is longer-running work: Rovo Work is built for autonomous tasks that run for hours rather than seconds, Rovo Code Search queries code, and the new Artifacts app saves and shares interactive AI output.
Atlassian says it shipped more than 120 enterprise capabilities in the twelve months before the conference. The Teamwork Graph now holds over 250 billion connections between people, work items, code, assets and data, indexes code down to individual functions, and pulls metadata in from BigQuery and Snowflake.
The MCP server and the 25 percent
The rebuilt Atlassian MCP server is the interoperability piece. It exposes Jira and Confluence context to external clients – Claude, Cursor, VS Code, OpenAI-based tooling – rather than locking agents inside Atlassian's own interface. Atlassian also claims the rebuild cuts token consumption by up to 25% compared with its previous benchmarks for Jira and Confluence tasks. That number is the vendor's own and arrives without a third-party measurement attached to it.
It is still worth converting into money, because token counts are the line item that decides whether an agent stays switched on. Take OpenAI's GPT-4o, published on the provider's pricing page at $2.50 per million input tokens and $10.00 per million output tokens. An agent workload of one million input and 100,000 output tokens per month costs $3.50 at those rates. A 25% cut takes it to roughly $2.63. Run the same arithmetic against GPT-4o mini, at $0.15 input and $0.60 output per million, and $0.21 becomes about $0.16. The percentage is identical; the sums are not. Efficiency work of this kind pays off most clearly when the model behind the agent is expensive, and less so when you are already running a cheap one.
Whether Atlassian routes a given task to a flagship or a small model matters for that bill more than the 25% does. More than 75% of Atlassian's enterprise customers already run multi-vendor AI foundation models, according to the company, so in practice the choice is yours to make and to audit.
The European questions that come with it
The conference was in Amsterdam, which is not incidental. European buyers tend to ask where an agent's processing happens before they hand it write access to production tickets, and agentic workflows make that question sharper than chatbot pilots ever did. An agent that reads and writes across Confluence, code and HR-adjacent metadata is not a demo.
Atlassian Cloud offers data residency options, including an EU region. Data residency answers where data is stored. It does not, by itself, answer where an AI feature sends prompts, which model provider processes them, or how long anything is retained. Those are separate answers, and for Rovo features they belong in a procurement checklist rather than a press release. If your organisation is worried about US CLOUD Act exposure, the model provider path is the part to trace, not only the storage bucket.
Regulation adds a second layer, and the timeline is easy to get wrong. Obligations for providers of general-purpose AI models have applied since 2 August 2025, and the transparency duties that sit alongside them went live on 2 August 2026. The current shape of that schedule comes from the Digital Omnibus package, Regulation (EU) 2026/1744. For a company deploying agents that touch employee work – task assignment, workload, evaluation – the AI Act's high-risk list has long included employment and worker management uses, and that is the category to check against your own deployment. GDPR Article 22 is the other one worth a look: it applies when automated processing has legal or similarly significant effects on a person. An agent that closes stale tickets is not that. An agent whose output feeds a performance review may be.
What to check before an agent gets write access
Four things, in this order. Which Rovo and AMP features are covered by your data residency configuration, and which are not. Which model providers receive your prompts for each task type. What admin controls exist to limit an agent's scope, and whether those limits are enforced by the system or by policy documents. And how long the audit trail of agent actions is retained, because that log is the artifact you will need if anyone asks what happened.
If you want to know what agentic workflows cost in tokens before you sign anything, we run those measurements ourselves on local and cloud models in AI Arena – a 16 GB RTX 5060 Ti rig with Ollama on one side and hosted APIs on the other. The gap between a vendor's benchmark and a production workload is usually visible within an afternoon.
The numbers to keep in mind
Atlassian cites Gartner's forecast that 40% of enterprise applications will include task-specific AI agents by the end of 2026, up from less than 5% in 2025. Its own platform claim is that 85% of Fortune 500 companies already run on Atlassian. Both figures come from the announcement, and neither has been independently audited – the same is true of the 25% token reduction, which is the number most likely to affect your bill.
Is AMP available to European customers?
AMP was rolled out across Atlassian Cloud, and Atlassian Cloud is sold and operated in the EU. Whether a specific Rovo or AMP capability processes data inside the EU depends on the product, your data residency configuration and the model provider behind each task. Get that confirmed in writing before an agent receives write permission.
How is AMP different from MCP?
MCP is the open standard for connecting a model to tools and data, originally created by Anthropic. Atlassian rebuilt its MCP server so external clients such as Claude, Cursor, VS Code and OpenAI-based tools can reach Jira and Confluence context. AMP sits above that: it is Atlassian's own framework for giving an agent an identity, limits and a record of actions inside Atlassian's products. Atlassian calls it a protocol; whether other vendors adopt it is a separate question from whether it works in Atlassian Cloud.
Does the 25% token saving apply to every workflow?
The figure is stated for Jira and Confluence tasks through the rebuilt MCP server, which is the path external tools use. The announcement gives one number without a per-client or per-task breakdown, so it should not be assumed across every agent workflow in your environment.
