# How to connect Atlassian MCP with ChatGPT Work

```json
{
  "title": "How to connect Atlassian MCP with ChatGPT Work",
  "toolkit": "Atlassian MCP",
  "toolkit_slug": "atlassian_mcp",
  "framework": "ChatGPT Work",
  "framework_slug": "chatgpt",
  "url": "https://composio.dev/toolkits/atlassian_mcp/framework/chatgpt",
  "markdown_url": "https://composio.dev/toolkits/atlassian_mcp/framework/chatgpt.md",
  "updated_at": "2026-09-01T05:32:42.301Z"
}
```

## Introduction

### How to connect Atlassian MCP with ChatGPT Work
[ChatGPT Work](https://openai.com/chatgpt-work/) is an agent inside ChatGPT built for your most ambitious work. It takes action across your apps and files, stays with a project for hours, and turns a goal into finished materials like sheets, slides, and docs - not just answers.
In this guide, I will explain the easiest and most secure way to connect your Atlassian account to ChatGPT Work via Composio Connect, so it can create jira issues, update your service tickets, search confluence pages, and open bitbucket pull requests through natural language commands without ever putting your account credentials at risk.

## Also integrate Atlassian MCP with

- [Claude Cowork](https://composio.dev/toolkits/atlassian_mcp/framework/claude-cowork)
- [Hermes](https://composio.dev/toolkits/atlassian_mcp/framework/hermes-agent)

## TL;DR

### Why use Composio over default connectors?
- Apps with read and write access. Default connectors mostly can read your data. Composio's Atlassian integration lets ChatGPT Work take actions like creating drafts, sending updates, labeling records, and more.
- 1,000+ SaaS toolkits out of the box. Composio gives you instant access to a vast catalog of pre-built connectors, from Gmail and Slack to Notion, Linear, and Salesforce.
- One MCP server for every app. Connect any of your applications on demand through a single endpoint, rather than juggling a separate server for each app.
- Smart, context-aware tool loading. Unlike traditional MCP servers that dump every available tool into the LLM context window, Composio searches for and loads only the tools relevant to the task at hand.
- Cross-app automation. Chain actions across multiple apps in a single run - fetch a thread, summarize it in Notion, and post highlights to Slack without leaving the conversation.

## Connect Atlassian MCP to ChatGPT Work

### Prerequisites
- A ChatGPT account with access to ChatGPT Work (rolling out across Pro, Enterprise, Edu, Plus, and Business plans). We will use the [ChatGPT desktop app](https://openai.com/chatgpt/download/), which is available on every plan.
- Access to the Atlassian workspace you want to connect.
- [Composio MCP](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=chatgpt&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fchatgpt).
Note: Composio connects through OAuth. You will be asked to sign in and approve specific permissions. Review the permission screen carefully if you are using a work account.
### Step-by-step: Connect Atlassian to ChatGPT Work
### 1. Open the MCP settings
In ChatGPT Work, go to Settings and open the Plugins section. Inside the Plugins page, click the MCP tab.
### 2. Add the server
Click Add server. In the Name field enter Composio, for Type select Streamable HTTP, and in the URL field paste the Composio MCP server URL:

```bash
https://connect.composio.dev/mcp
```

## What is the Atlassian MCP server, and what's possible with it?

The Atlassian MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Atlassian account. It provides structured and secure access so your agent can perform Atlassian operations on your behalf.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `ATLASSIAN_MCP_ADD_COMMENT_TO_JIRA_ISSUE` | Addcommenttojiraissue | Add or update a comment on a Jira issue |
| `ATLASSIAN_MCP_ADD_TEAMWORK_GRAPH_CONTEXT` | Addteamworkgraphcontext | Adds a relationship between two entities in the Teamwork Graph (e.g. linking two Jira work items, marking one as blocking another, attaching a remote link, or connecting a Jira work item to an Atlas project or goal). |
| `ATLASSIAN_MCP_ADD_WORKLOG_TO_JIRA_ISSUE` | Addworklogtojiraissue | Add or update a worklog on a Jira issue. When worklogId is provided, updates that worklog; |
| `ATLASSIAN_MCP_ATLASSIAN_USER_INFO` | Atlassianuserinfo | Get current user info |
| `ATLASSIAN_MCP_CREATE_COMPASS_COMPONENT` | Createcompasscomponent | Create a new Compass component |
| `ATLASSIAN_MCP_CREATE_COMPASS_COMPONENT_RELATIONSHIP` | Createcompasscomponentrelationship | Create a relationship between Compass components |
| `ATLASSIAN_MCP_CREATE_COMPASS_CUSTOM_FIELD_DEFINITION` | Createcompasscustomfielddefinition | Create a custom field definition in Compass |
| `ATLASSIAN_MCP_CREATE_CONFLUENCE_FOOTER_COMMENT` | Createconfluencefootercomment | Create a footer comment on a page or blog post |
| `ATLASSIAN_MCP_CREATE_CONFLUENCE_INLINE_COMMENT` | Createconfluenceinlinecomment | Create an inline comment on specific text in a page or blog post. For top-level comments, provide pageId and inlineCommentProperties (text selection + match counts). For replies, provide parentCommentId only (no pageId or inlineCommentProperties). You must first fetch the page content (e.g. using getConfluencePage) to find the exact text and count how many times it appears. Incorrect or missing inlineCommentProperties can result in a 400 error from the Confluence API. |
| `ATLASSIAN_MCP_CREATE_CONFLUENCE_PAGE` | Createconfluencepage | Create a Confluence page or blog post |
| `ATLASSIAN_MCP_CREATE_ISSUE_LINK` | Createissuelink | Create a link between two Jira issues. For directional link types (e.g. Blocks): inwardIssue = issue that blocks, outwardIssue = issue that is blocked (e.g. "A is blocked by B" → inwardIssue: B, outwardIssue: A). Use getIssueLinkTypes if link type is unknown. |
| `ATLASSIAN_MCP_CREATE_JIRA_ISSUE` | Createjiraissue | Create a Jira issue. Use additional_fields to set any Jira field that does not have its own parameter (e.g. custom fields, priority, components). |
| `ATLASSIAN_MCP_EDIT_JIRA_ISSUE` | Editjiraissue | Update issue. After updating, returns the issue using the same default read fields as getJiraIssue (summary, description, status, issuetype, priority, labels, components, assignee, reporter, created, updated, resolution, project). Use getJiraIssue with fields ["*all"] or a custom list if you need more. |
| `ATLASSIAN_MCP_FETCH` | Fetch | Get details of a Jira issue or Confluence page by ARI (Atlassian Resource Identifier), if the id is not an ARI, then use a different tool to fetch the content |
| `ATLASSIAN_MCP_GET_ACCESSIBLE_ATLASSIAN_RESOURCES` | Getaccessibleatlassianresources | Get cloudId to make tool calls. When a link is provided (e.g. https://site.atlassian.net/*), try passing the site hostname (e.g. site.atlassian.net) as cloudId to other tools first; if that fails, use this tool to list accessible resources. |
| `ATLASSIAN_MCP_GET_COMPASS_COMPONENT` | Getcompasscomponent | Get a Compass component by ID |
| `ATLASSIAN_MCP_GET_COMPASS_COMPONENTS` | Getcompasscomponents | Get a list of Compass components |
| `ATLASSIAN_MCP_GET_COMPASS_CUSTOM_FIELD_DEFINITIONS` | Getcompasscustomfielddefinitions | Get a list of Compass custom field definitions |
| `ATLASSIAN_MCP_GET_CONFLUENCE_COMMENT_CHILDREN` | Getconfluencecommentchildren | Get reply(child) comments for a comment |
| `ATLASSIAN_MCP_GET_CONFLUENCE_PAGE` | Getconfluencepage | Get a Confluence page or blog post by ID, including body content. |
| `ATLASSIAN_MCP_GET_CONFLUENCE_PAGE_DESCENDANTS` | Getconfluencepagedescendants | Get child pages of specified page |
| `ATLASSIAN_MCP_GET_CONFLUENCE_PAGE_FOOTER_COMMENTS` | Getconfluencepagefootercomments | Get footer comments for a page or blog post |
| `ATLASSIAN_MCP_GET_CONFLUENCE_PAGE_INLINE_COMMENTS` | Getconfluencepageinlinecomments | Get inline comments for a page or blog post |
| `ATLASSIAN_MCP_GET_CONFLUENCE_SPACES` | Getconfluencespaces | Get spaces |
| `ATLASSIAN_MCP_GET_ISSUE_LINK_TYPES` | Getissuelinktypes | Get available Jira issue link types (e.g. Blocks, Duplicate, Clones, Relates). For createIssueLink: inwardIssue = blocker, outwardIssue = blocked (e.g. "A is blocked by B" → inwardIssue: B, outwardIssue: A). |
| `ATLASSIAN_MCP_GET_JIRA_ISSUE` | Getjiraissue | Get issue details |
| `ATLASSIAN_MCP_GET_JIRA_ISSUE_REMOTE_ISSUE_LINKS` | Getjiraissueremoteissuelinks | Get remote links |
| `ATLASSIAN_MCP_GET_JIRA_ISSUE_TYPE_META_WITH_FIELDS` | Getjiraissuetypemetawithfields | Get field metadata |
| `ATLASSIAN_MCP_GET_JIRA_PROJECT_ISSUE_TYPES_METADATA` | Getjiraprojectissuetypesmetadata | Get issue types |
| `ATLASSIAN_MCP_GET_PAGES_IN_CONFLUENCE_SPACE` | Getpagesinconfluencespace | Get pages or blog posts in a space |
| `ATLASSIAN_MCP_GET_TEAMWORK_GRAPH_CONTEXT` | Getteamworkgraphcontext | Retrieves connected context from Teamwork Graph for any Atlassian entity. Returns all relationships and linked objects within one traversal – including cross-product and third-party connections. Use when the answer requires connections between entities, not just a single entity's fields. Supported entry points: Jira: issues, projects, sprints, versions, comments Confluence: pages, blogposts, whiteboards, databases, spaces Goals, Projects, Focus Areas, Tags and updates People: users, teams, organisations DevOps: PRs, repos, deployments, services, builds, designs Loom: videos, meetings Compass: components Assets: objects Incidents, conversations, calendar events, external documents After calling this tool, call getTeamworkGraphObject on returned ARIs to get full content. |
| `ATLASSIAN_MCP_GET_TEAMWORK_GRAPH_OBJECT` | Getteamworkgraphobject | Fetches the entire available data for one or more objects (Atlassian or third-party) using their ARIs or URLs. Use for the objects gathered from getTeamworkGraphContext tool. |
| `ATLASSIAN_MCP_GET_TRANSITIONS_FOR_JIRA_ISSUE` | Gettransitionsforjiraissue | Get transitions |
| `ATLASSIAN_MCP_GET_VISIBLE_JIRA_PROJECTS` | Getvisiblejiraprojects | Get projects |
| `ATLASSIAN_MCP_LOOKUP_JIRA_ACCOUNT_ID` | Lookupjiraaccountid | Lookup user IDs |
| `ATLASSIAN_MCP_SEARCH` | Search | Search Jira and Confluence using Rovo Search, ALWAYS use this tool to search for Jira and Confluence content unless the word CQL or JQL is used in the context |
| `ATLASSIAN_MCP_SEARCH_CONFLUENCE_USING_CQL` | Searchconfluenceusingcql | Search Confluence content (pages, blog posts, comments, attachments) using CQL (Confluence Query Language). CQL is specific to Confluence and is not interchangeable with JQL. |
| `ATLASSIAN_MCP_SEARCH_JIRA_ISSUES_USING_JQL` | Searchjiraissuesusingjql | Search issues with JQL, total counts only when explicitly requested. |
| `ATLASSIAN_MCP_TRANSITION_JIRA_ISSUE` | Transitionjiraissue | Transition issue status |
| `ATLASSIAN_MCP_UPDATE_CONFLUENCE_PAGE` | Updateconfluencepage | Update a Confluence page or blog post |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

Once connected, ChatGPT Work can access the Atlassian MCP server via Composio to run actions that you authorize, directly in your workspace.

## Complete Code

None listed.

## How to build Atlassian MCP Agent with another framework

- [Claude Cowork](https://composio.dev/toolkits/atlassian_mcp/framework/claude-cowork)
- [Hermes](https://composio.dev/toolkits/atlassian_mcp/framework/hermes-agent)

## Related Toolkits

- [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
- [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.
- [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.
- [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.
- [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.
- [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently.
- [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place.
- [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.
- [Amazing Marvin](https://composio.dev/toolkits/amazing_marvin) - Amazing Marvin is a personal productivity app for tasks, projects, habits, planning, time tracking, and rewards. It helps you build a flexible workflow that matches how you actually work.
- [AnyDB](https://composio.dev/toolkits/any_db) - AnyDB is a flexible collaborative database platform for organizing records, files, and automated workflows. It helps teams centralize data, collaborate on records, and automate routine tasks.
- [ApptiveGrid](https://composio.dev/toolkits/apptivegrid) - ApptiveGrid is a collaborative no-code database and app platform for spaces, grids, forms, and structured records. It helps teams organize operational data, collect inputs, and build lightweight business apps without custom backend work.
- [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Beeminder](https://composio.dev/toolkits/beeminder) - Beeminder is an online goal-tracking platform that uses monetary pledges to keep you motivated. Stay accountable and hit your targets with real financial incentives.
- [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions.
- [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date.
- [Breeze](https://composio.dev/toolkits/breeze) - Breeze is a project management platform designed to help teams plan, track, and collaborate on projects. It streamlines workflows and keeps everyone on the same page.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Atlassian MCP?

With a standalone Atlassian MCP server, the agents and LLMs can only access a fixed set of Atlassian tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Atlassian and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with ChatGPT Work?

Yes, you can. ChatGPT Work fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Atlassian tools.

### Can I manage the permissions and scopes for Atlassian while using Tool Router?

Yes, absolutely. You can configure which Atlassian scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Atlassian data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)