TWG CLI
A command-line tool introduced by Atlassian that gives AI coding agents access to work context such as Jira, Confluence and Bitbucket. It is built on the permission-aware Teamwork Graph.
Timeline (last 90 days)
TWG CLI is a command-line tool launched by Atlassian that lets AI coding agents access the user's Atlassian work context, built on top of the permission-aware Teamwork Graph.
TWG CLI covers Atlassian products including Jira, Confluence, Bitbucket, Jira Service Management, Assets, Loom, Trello, Rovo Search and Goals.
TWG CLI can be used with Claude Code, Codex, Gemini CLI, Cursor and any other agent that can execute shell commands.
TWG CLI is currently in the Atlassian Early Access Program stage, free to use, with the official note that some features may later become paid.
TWG CLI runs as a local binary, whereas Rovo MCP Server is an Atlassian cloud-hosted endpoint.
TWG CLI login uses browser OAuth, and PR features additionally require a Bitbucket API token; Rovo MCP Server uses OAuth 2.1, and Bitbucket and JSM tools require API token authentication.
The token cost of the content itself is the same on both MCP and TWG sides, with similar consumption for long Jira descriptions or large PR diffs.
For coding agents that live in the terminal, the CLI form is more natural than an MCP server, because it loads almost no context at startup and discovers commands on demand via --help.
All Facts (8)
TWG CLI is a command-line tool launched by Atlassian that lets AI coding agents access the user's Atlassian work context, built on top of the permission-aware Teamwork Graph.
50%UnverifiedTWG CLI covers Atlassian products including Jira, Confluence, Bitbucket, Jira Service Management, Assets, Loom, Trello, Rovo Search and Goals.
50%UnverifiedTWG CLI can be used with Claude Code, Codex, Gemini CLI, Cursor and any other agent that can execute shell commands.
50%UnverifiedTWG CLI is currently in the Atlassian Early Access Program stage, free to use, with the official note that some features may later become paid.
50%UnverifiedTWG CLI runs as a local binary, whereas Rovo MCP Server is an Atlassian cloud-hosted endpoint.
50%UnverifiedTWG CLI login uses browser OAuth, and PR features additionally require a Bitbucket API token; Rovo MCP Server uses OAuth 2.1, and Bitbucket and JSM tools require API token authentication.
50%UnverifiedThe token cost of the content itself is the same on both MCP and TWG sides, with similar consumption for long Jira descriptions or large PR diffs.
50%UnverifiedFor coding agents that live in the terminal, the CLI form is more natural than an MCP server, because it loads almost no context at startup and discovers commands on demand via --help.
50%