Studio, Forge, MCP, TWG, Dev CLI, what’s the difference? [Champions Slack Insider]

[#1]

A discussion sparked by @Rebekka Heilmann _viadee_ illustrated a growing challenge:

As terms like Studio, Forge, MCP, Teamwork Graph, Teamwork Graph CLI, and Rovo Dev CLI appear more frequently in conversations, it becomes increasingly difficult to understand how they relate to one another.

The technology itself is becoming easier to use. The naming? Not so much. Let's untangle it.

Let's Build the City

Think of Atlassian's AI ecosystem as a city. Most people use the roads, buildings, and services every day without thinking much about how the city itself works.

Let's start with the piece that connects everything.

Teamwork Graph: The Map and Road Network

At the center of the city is Teamwork Graph (TWG). Think of TWG as both:

• The city's master map

• The network of roads 

It helps AI understand how:

• People relate to teams

• Teams relate to projects

• Projects relate to goals

• Knowledge relates to work

• Work relates to customers

Teamwork Graph exposes relationships. Without it, Rovo would see thousands of disconnected buildings. With it, Rovo can understand how the people, places, and objects in the city relate to one another. Most users never interact with Teamwork Graph directly, but many AI features rely on it behind the scenes. 

Rovo Chat: The Tour Guide

Most users first experience AI through Rovo Chat. Think of Rovo Chat as the tour guide. You ask a question, and it:

• Looks at the city map

• Travels the roads

• Confirms your destination

• Takes you there

The guide does not own the map. The guide uses the map to help you find what you're looking for.

Studio: The City Planning Office

Eventually, people want AI to do more than answer questions. They want it to take action or answer more complex questions that are specific to their business. Studio is the city planning office where you design and manage tools such as:

• Company Hubs – The city's information center where people find trusted resources and announcements.

• Agents – Assistants that help people find information, answer questions, and complete tasks.

• Service Agents (JSM only) – Customer support assistants that help answer questions, guide users, and support service requests.

• Automation Flows – Workers that handle repetitive tasks automatically so people don't have to.

• App Builder – An AI architect that helps design custom apps using natural language.

• Assets (JSM only) – The city's inventory showing what exists, who owns it, and how everything is connected.

You're deciding:

• What should be built

• How people should move through the city

• Where services should be connected

Find information → Get help → Receive support → Automate work → Build solutions → Manage the environment.

App Builder: The Architect

Inside Studio is App Builder. Think of App Builder as an architect who can quickly sketch a building after hearing your idea.

For example:

Build an app that tracks contractor access across projects.

For simpler buildings, the architect can often create the plans and hand them directly to the construction crew through App Builder's integration with Forge. That may be enough to create and deploy a basic app with only a little additional work.

For more complex buildings, the architect can create a strong starting design, but specialists may still need to refine the plans and add advanced features that were not included in the original sketch. That's where deeper Forge development comes in.

App Builder makes building apps more accessible, but it does not eliminate the need for development knowledge when requirements become more sophisticated.

Forge: The Construction Crew

If App Builder is the architect, Forge is the construction crew, tool yard, and building site. Forge is Atlassian's application platform and the place where apps are constructed and run. Whether an app was:

• Generated through App Builder

• Created directly by developers

• Published to the Marketplace

it ultimately gets built and operates on Forge.

The crew has access to the building materials, specialized equipment, and advanced construction techniques needed to create everything from a simple shed to a skyscraper.

Rovo Dev CLI: The Construction Foreman

Think of Rovo Dev CLI as an AI construction foreman enabling the construction crew to build. It helps:

• Write code

• Review code

• Troubleshoot problems

• Build applications

Atlassian describes Rovo Dev CLI as bringing AI capabilities to the terminal for tasks such as generating, reviewing, refactoring, debugging, documenting, and testing code.

Side Note: CLI stands for Command Line Interface. Most apps give you menus, icons, and buttons to click. A CLI gives you a text box where you type instructions directly to the computer.

In our city analogy, a CLI is like giving a construction worker a radio and task list instead of making them walk into the planning office for each task to get instructions.

Model Context Protocol: Border Patrol

Now imagine someone outside the city wants access. Maybe they're using:

• Claude
• Cursor
• Windsurf
• Another MCP-compatible AI tool

Think of the Atlassian/Rovo MCP Server as the city's border crossing and MCP as the border patrol officers. Every visitor arriving from another AI city must pass through border control. The officers:

• Check identity
• Verify permissions
• Prevent unauthorized entry
• Determine what areas can be accessed
• Ensure visitors follow the city's rules

MCP does not contain the city. It controls access to the city. The protocol is the agreed-upon process that allows different AI systems to communicate with one another.

Once admitted, external AI systems can travel the city's roads, access approved destinations, and use supported tools—including Teamwork Graph capabilities when available.

Teamwork Graph CLI: The Road Worker

This is where the analogy gets interesting. Many people assume TWG CLI is just another way to access Atlassian. It's more specialized than that. Think of Teamwork Graph CLI as a road worker.

Its job is not to build entirely new destinations. Instead, Teamwork Graph CLI helps developers and coding agents connect to and work within the city's existing roads and routes. While Teamwork Graph provides the map and road network, Forge is the construction crew building new structures, and Rovo Dev CLI is the AI foreman helping coordinate the construction effort.

That's why the two CLIs often get confused. They're both tools for builders, but they help with different jobs.

The Breakdown

• Teamwork Graph = City map and road network

• Rovo Chat = Tour guide

• Studio = City planning office

• App Builder = AI architect

• Forge = Construction crew, tool yard, and building site

• Rovo Dev CLI = AI construction foreman

• MCP = Border patrol gates

• Teamwork Graph CLI = Road engineer  

Champion Takeaway

The naming becomes much easier once you stop thinking about products and start thinking about responsibilities. Ask yourself:

Am I trying to understand relationships between people, projects, and knowledge?
→ Think Teamwork Graph.

Am I building something simple?
→ Think Studio, App Builder

Am I building something complex?
→ Think Forge.

Am I writing, reviewing, or troubleshooting software?
→ Think Rovo Dev CLI.

Am I connecting an external AI tool to Atlassian?
→ Think MCP.

Am I working directly with Teamwork Graph from a terminal or coding-agent workflow?
→ Think Teamwork Graph CLI.

They're different parts of the same city, working together to help people build solutions, understand organizational context, access information, and develop software.