Hello Atlassian Community,
Camilo from the Studio team here.
We’re excited to share that we’re expanding the set of read-only MCP tools available in Studio, making it easier for makers to connect agents to more of the apps they already use every day.
Starting with this release, Studio users will have access to a new set of curated read-only MCP servers by default. This means agents can discover and use information from more tools out of the box, without requiring the same setup overhead that custom MCP connections often involve.
What’s changing?
We’re enabling an initial set of curated read-only MCP servers for these apps:
-
Slack: Bring channel and workspace context into agent workflows.
-
Notion: Help agents reference documentation and structured workspace knowledge.
-
Figma: Give agents access to design context and supporting artifacts.
-
Canva: Expand access to visual content and creative assets.
-
Asana: Access external task and project data from Asana workspaces
-
HubSpot: Make CRM context easier to bring into agent experiences.
-
New Relic: Allow agents to reference observability and operational insights.
-
Gamma: Enable access to presentation and content artifacts.
-
Box: Let agents work with documents and shared file context.
-
Lovable: Expand the set of modern tools agents can read from in Studio.
These servers are curated and read-only, which helps us make useful tools broadly available while maintaining a strong trust and safety posture (Find out more about read-only MCP tools here: https://support.atlassian.com/organization-administration/docs/understand-read-only-mcp-integrations/)
What do you need to do?
You don’t need to do anything to get started.
These read-only MCP servers will be available by default for all Studio users as they roll out. When building an agent in Atlassian, including in Studio, look for the available MCP tools in the agent’s tool selection or configuration experience. Once available in your environment, you can start using them with your agents to bring in more external context across research, content creation, planning, and other common workflows.
If your agent needs to take action in one of these apps, rather than only read information, ask your organisation’s Atlassian administrator about enabling the relevant write tools. Write tools require admin review and approval before they can be used.
To request access to write tools to your administrator, find the list of curated MCP servers in the tools directory in Studio by clicking on the + icon next to MCP (Model Context Protocol), and click on the Request button of the relevant MCP server.
What’s next?
This is the beginning of a broader effort to scale Studio’s MCP catalogue. We’re working toward a future where Studio users can benefit from a much larger set of curated MCP servers and tools by default, with less manual setup and faster availability for useful new integrations.
We’d love to hear what read-only tools you’d like to see next and how you’re using MCP-powered agents today. Feel free to share feedback or questions below.
Best regards,
The Atlassian Studio Team
