Addcommenttojiraissue
Add or update a comment on a Jira issue
ActionTry it
Integrate Atlassian MCP
with your AI CRM
Atlassian Rovo MCP connects agents to Jira, Jira Service Management, Confluence, Bitbucket, Compass, and Teamwork Graph workflows while respecting existing user permissions.
Explore Triggers and Actions
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).
ActionTry it
Addworklogtojiraissue
Add or update a worklog on a Jira issue. When worklogId is provided, updates that worklog;
ActionTry it
Atlassianuserinfo
Get current user info
ActionTry it
Createcompasscomponent
Create a new Compass component
ActionTry it
Createcompasscomponentrelationship
Create a relationship between Compass components
ActionTry it
Createcompasscustomfielddefinition
Create a custom field definition in Compass
ActionTry it
Createconfluencefootercomment
Create a footer comment on a page or blog post
ActionTry it
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.
ActionTry it
Createconfluencepage
Create a Confluence page or blog post
ActionTry it
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.
ActionTry it
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).
ActionTry it
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.
ActionTry it
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
ActionTry it
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.
ActionTry it
Getcompasscomponent
Get a Compass component by ID
ActionTry it
Getcompasscomponents
Get a list of Compass components
ActionTry it
Getcompasscustomfielddefinitions
Get a list of Compass custom field definitions
ActionTry it
Getconfluencecommentchildren
Get reply(child) comments for a comment
ActionTry it
Getconfluencepage
Get a Confluence page or blog post by ID, including body content.
ActionTry it
Getconfluencepagedescendants
Get child pages of specified page
ActionTry it
Getconfluencepagefootercomments
Get footer comments for a page or blog post
ActionTry it
Getconfluencepageinlinecomments
Get inline comments for a page or blog post
ActionTry it
Getconfluencespaces
Get spaces
ActionTry it
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).
ActionTry it
Getjiraissue
Get issue details
ActionTry it
Getjiraissueremoteissuelinks
Get remote links
ActionTry it
Getjiraissuetypemetawithfields
Get field metadata
ActionTry it
Getjiraprojectissuetypesmetadata
Get issue types
ActionTry it
Getpagesinconfluencespace
Get pages or blog posts in a space
ActionTry it
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.
ActionTry it
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.
ActionTry it
Gettransitionsforjiraissue
Get transitions
ActionTry it
Getvisiblejiraprojects
Get projects
ActionTry it
Lookupjiraaccountid
Lookup user IDs
ActionTry it
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
ActionTry it
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.
ActionTry it
Searchjiraissuesusingjql
Search issues with JQL, total counts only when explicitly requested.
ActionTry it
Transitionjiraissue
Transition issue status
ActionTry it
Updateconfluencepage
Update a Confluence page or blog post
ActionTry it
How the Atlassian MCP integration works
The Atlassian MCP integration connects your Dench AI CRM directly to Atlassian MCP, so agents can read and act on your Atlassian MCP data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
40 actions are available for agents to invoke on your behalf. Every call runs through Atlassian MCP's own authorization, scoped to the account you connect.
Set up Atlassian MCP in Dench
- 1
Sign in to your Dench workspace and open Integrations.
- 2
Find Atlassian MCP and click Connect — you'll authorize access through Atlassian MCP's own sign-in flow. No API keys or code required.
- 3
Ask an agent to use Atlassian MCP in chat, or call it from an automation.
- 4
Manage or disconnect the connection any time from workspace settings.
Frequently asked questions
How does the Atlassian MCP integration work with Dench?
The Dench Atlassian MCP integration connects your AI CRM to Atlassian MCP, so AI agents can work with your Atlassian MCP data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
What actions can AI agents perform with Atlassian MCP via Dench?
The Atlassian MCP integration currently exposes 40 actions, including Addcommenttojiraissue, Addteamworkgraphcontext, Addworklogtojiraissue, Atlassianuserinfo, Createcompasscomponent, and Createcompasscomponentrelationship. Agents invoke them on your behalf from chat or from automations.
Do I need to write code to connect Atlassian MCP to Dench?
No. You connect Atlassian MCP from your Dench workspace using Atlassian MCP's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Is the Atlassian MCP integration secure?
Connections are authorized through Atlassian MCP's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Atlassian MCP connection from your workspace settings at any time.