Hi community,
Strategy work has some of the most important context in your organization: what you are aiming for, how work is tracking, who owns it, how teams are staffed, and how each initiative connects back to company priorities.
That context is now easier to bring into the AI tools your teams already use. Strategy Collection tools for Focus, Goals, Projects, and Talent are now available on the Atlassian MCP Server, so MCP-compatible clients and agents can use supported tools to securely search, read, create, update, and connect strategic context on your behalf.
This means your agent can move beyond isolated prompts and start working with the real system of record: focus areas, goals, projects, people and roles, Jira work, and Confluence strategy docs.
Remind me, what is MCP?
The Model Context Protocol is an open standard that lets AI clients connect to the tools where your work happens.
The Atlassian MCP Server securely connects Atlassian apps with your LLM, IDE, or agent platform of choice. It uses OAuth and your existing Atlassian permissions, so an agent only sees and changes what you are allowed to access.
MCP is not just for Strategy Collection. The Atlassian Rovo MCP Server also supports connected workflows across Atlassian apps like Jira and Confluence, which is what makes these strategy tools especially useful: an agent can read the strategy, inspect the delivery work, draft an update, and connect the right objects together.
Where this works today
You can connect the Atlassian MCP Server to supported MCP clients and agent environments, including tools such as Cursor, VS Code/GitHub Copilot, ChatGPT, Claude, and CLI-based agents that support remote MCP, as well as Atlassian’s Rovo Slack app.
Capability varies by client and surface. Some clients are better for read and research workflows; others can support create and update workflows once you have authenticated and approved the relevant tools. Rovo experiences inside Atlassian products are also expanding over time, but exact support can vary by product surface and admin configuration.
For setup and the latest supported-client guidance, start with Atlassian's MCP page and the supported tools documentation.
What's available
The Strategy Collection toolset covers four major areas:
Focus
Use Focus tools to explore and manage strategic focus areas and their hierarchies.
searchFocusAreas and getFocusArea help agents find focus areas, understand health and status, inspect child focus areas, and pull in connected goals and work.getFocusAreaTypes helps agents understand the focus-area hierarchy your site uses.createFocusArea and updateFocusArea help create or edit the core details of a focus area.createFocusAreaStatusUpdate helps post a new status update.linkToFocusArea helps connect goals, projects, Jira work, or child focus areas.
Talent
Use Talent tools to understand people, roles, skills, and staffing context.
getTalentUser, getTalentPosition, and searchTalentPositions help agents understand users, roles, reporting lines, locations, levels, and job families.getTalentPositionsByEntity helps inspect positions connected to managers or focus areas.getTalentGroupMetrics helps summarize headcount and open or filled positions by fields such as country, level, manager, or focus area.getTalentFields helps agents discover which fields and filters are available before building a query.createTalentSkill, updateTalentWorkerSkillMappings, and updateTalentPositionFocusAreaMappings help maintain skills and focus-area allocation context where enabled.
Goals
Use Goals tools to find, inspect, create, update, and connect goals.
searchGoals and getGoal help agents find the right goals and understand ownership, status, hierarchy, and metrics.getGoalUpdate helps agents inspect a specific update.getGoalTypes helps agents understand which goal types are available before creating anything.createGoal and createGoalUpdate help create goals and post progress updates.addConnectionsToGoals helps connect goals to projects, teams, Jira work, tags, followers, and focus areas.
Projects
Use Projects tools to review, create, update, and connect Atlassian projects.
searchProjects and getProject help agents find projects by name, owner, team, tag, status, or connected goal.getProjectUpdate helps agents inspect weekly updates, notes, milestones, and comments.createProject and createProjectUpdate help create a project or post a progress update.addConnectionsToProjects helps connect projects to goals, Jira work, contributors, teams, tags, focus areas, and external links.
For the full, up-to-date reference, including parameters, scopes, and availability, use the supported tools documentation.
What can you do with it?
Here are a few workflows you can try in plain language.
Turn strategy into connected execution
"Read this Confluence strategy doc, find the matching focus area, draft a goal for the next quarter, create it, and connect it to the relevant focus area and Jira work."
The agent can use Confluence for strategy context, Focus for strategic structure, Goals for the outcome, and Jira for the delivery work.
Draft a weekly leadership readout
"Summarize the health, status changes, risks, and next actions across my focus areas, connected goals, projects, and Jira work."
Instead of assembling a readout from memory, the agent can inspect the latest updates and connected work before drafting a summary.
Spot "green on the outside, red on the inside" risk
"Find focus areas that are marked on track but have connected Jira work or projects that are slipping."
The agent can compare the high-level health signal with the status of underlying goals, projects, and work items, then highlight mismatches before they surprise your team.
Create or align a project to the right strategy
"Create a project for the billing migration, connect it to the Payments focus area, link it to the goal for reducing support tickets, and add the relevant Jira work."
This is where the connected graph becomes powerful: the agent can help create the project and wire it into the existing strategic context instead of leaving it as an empty shell.
Prepare a portfolio risk and dependency update
"For the projects owned by my team, find off-track dependencies and risks, then draft a project update I can review."
The agent can search projects, inspect risks and dependencies, bring in related goals, and produce a progress update grounded in evidence.
Understand staffing and focus-area coverage
"How many engineers are allocated to the ADO portfolio, where do we have open roles, and which focus areas look under-supported?"
Talent and Focus tools can help your agent build a staffing lens on top of your strategy, so business and operations leaders can compare commitments with people and roles.
Improve strategy data quality
"Find goals and projects missing owners, stale updates, or disconnected work, and suggest what should be cleaned up."
Agents are only as useful as the context they can access. MCP makes it easier to audit and improve the strategy graph that future AI workflows will depend on.
How to get started
- Connect your client to
https://mcp.atlassian.com/v2/mcp - Sign in when your client starts the Atlassian authentication flow.
- Confirm that your admin has enabled the tools and scopes your workflow needs.
- Start with a read-only prompt, such as "Find my focus areas and summarize the latest updates."
- Move to create or update workflows once you are comfortable reviewing the agent's plan and output.
You can also use the one-click client setup links and guidance on Atlassian's MCP page.
Calls run within your existing permissions and your organization's admin controls. Usage is also subject to the current MCP rate limits and product availability documented by Atlassian.
Continuing our MCP momentum
This release continues Atlassian's broader investment in MCP as a way to make teamwork context available wherever teams use AI.
We are continuously expanding MCP capabilities to support deeper, connected workflows. Upcoming additions will broaden read coverage, improve filtering, expand write and update capabilities, and add deeper support for strategy concepts customers care about, including metrics and metric values, risks, dependencies, and focus areas.
MCP currently only supports single site authorisation. We are shipping multi-site authorisation very soon to make your journeys even smoother.
The goal is not MCP instead of product experiences. It is to make the underlying teamwork and strategy primitives available earlier, learn from real workflows, and then bring those learnings back into Rovo, Studio, Automation, dashboards, and Atlassian product experiences.
We'd love your feedback
Try these tools on real work and tell us what happens.
- What is the first Strategy Collection workflow you would augment with an agent?
- Where did the agent get useful context from Focus, Goals, Projects, Talent, Jira, or Confluence?
- Where did the journey stop because a tool, permission, or surface was missing?
- What create or update actions would you trust an agent to take after review?
- Where should agents not act without a human in the loop?
If you would be interested in future research, usability testing, or feedback sessions for Strategy Collection AI workflows, let us know in the comments as well.
We read every reply, and this feedback helps shape what we prioritize next.
As always, thank you for being part of the Atlassian Community.
