The Jira MCP server is Atlassian's hosted Rovo MCP server, which lets an AI agent or coding app read and update Jira, Confluence and other Atlassian products. Point any MCP-capable app at https://mcp.atlassian.com/v2/mcp, sign in with OAuth 2.1, and the agent can act only within your existing Jira permissions.
| Item | What Atlassian documents |
|---|---|
| Endpoint | https://mcp.atlassian.com/v2/mcp |
| Sign-in | OAuth 2.1; API token authentication also available as an option |
| Products | Jira, Jira Service Management, Confluence, Bitbucket, Projects, Goals, plus Loom recordings |
| Permissions | Actions respect each user's existing access controls |
| Off by default | The delete_jira and manage_jira tool groups |
| Usage | Calls use Rovo credits, per Atlassian's usage limits page |
Updated
MCP, short for Model Context Protocol, is a standard way for AI apps to call outside tools. Atlassian runs its own MCP server in the cloud, so there is nothing to install: your agent connects over the internet and asks you to sign in. Use the filter below to see exactly which Jira actions an agent can take, grouped the way Atlassian groups their permissions.
Every Jira tool Atlassian lists for its MCP server. Filter by permission group or type part of a name.
52 tools shown
getJiraIssuelistJiraProjectslistJiraProjectIssueTypesMetadatagetJiraIssueTypeMetaWithFieldslistJiraIssueTransitionslistJiraIssueLinkTypeslistJiraIssueRemoteIssueLinkslistJiraIssueWorklogslookupJiraAccountIdlistJiraIssueAssignableUserslistJiraIssueCommentslistJiraIssueChangelogsgetJiraCurrentUsergetJiraUserlistJiraStatuseslistJiraProjectComponentsgetJiraProjectVersionsgetJiraProjectVersionRelatedWorklistJiraBoardsgetJiraBoardConfiggetJiraBoardIssueDatagetJiraBoardSprintDatalistJiraBoardSprintslistJiraFilterslistJiraDashboardsgetJiraEntityPropertydownloadJiraIssueAttachmentsearchJiraIssuesUsingJqlcreateJiraIssueeditJiraIssuetransitionJiraIssueaddOrEditJiraIssueCommentaddOrEditJiraIssueWorklogcreateJiraIssueLinkcreateJiraIssueRemoteIssueLinkuploadAttachmentToJiraIssuewatchJiraIssuemanageJiraProjectVersionmanageJiraProjectVersionRelatedWorkmanageJiraSprintcreateJiraBoardeditJiraEntityPropertyconvertJiraIssueHierarchydeleteJiraIssuedeleteJiraCommentdeleteJiraIssueAttachmentcreateJiraProjectupdateJiraProjectgetJiraWorkflowsgetJiraWorkflowEditorLinkgetJiraScreenupdateJiraScreenMost MCP apps take a server name and a URL. This is the shape VS Code uses in .vscode/mcp.json, with servers in a top-level servers object.
No token goes in the file. The app opens Atlassian's sign-in page the first time it connects.
{
"servers": {
"atlassian": {
"type": "http",
"url": "https://mcp.atlassian.com/v2/mcp"
}
}
}searchJiraIssuesUsingJql takes Jira Query Language, the same syntax as Jira's advanced search.
project = WEB AND issuetype = Bug AND statusCategory != Done ORDER BY priority DESCIn Atlassian Administration, under Connectors and then Atlassian MCP server, an org admin can untick Allow Atlassian supported domains and add only trusted domains. Those domain rules apply to OAuth 2.1 sign-ins.
The same screen has an Authentication section where API token sign-in can be switched on or off. IP allowlists are managed elsewhere in Atlassian Administration and apply to both sign-in methods.
Ask for a read-only summary first, for example the unresolved issues assigned to you this sprint. Read tools like searchJiraIssuesUsingJql and getJiraIssue show whether the agent picks the right project before it can change anything.
Yes. Atlassian hosts the Atlassian Rovo MCP server, which covers Jira along with Confluence, Bitbucket and other products. Community-built Jira MCP servers also exist, but the official one needs no install and uses Atlassian's own sign-in.
With OAuth 2.1: your MCP app opens an Atlassian sign-in page and you approve access. Atlassian also documents API token authentication as an option, which an org admin can turn on or off.
Only if enabled. Atlassian lists deleteJiraIssue in the delete_jira group and project-level tools in the manage_jira group, and both groups are disabled by default.
No. Atlassian says OAuth ensures all actions respect users' existing access controls and permissions, so the agent can reach only what your account can reach.
Atlassian says calls consume Rovo credits, scaling with data volume and reasoning complexity, and points to its Rovo usage limits page for the thresholds. Check that page for your plan, as of October 2026.
Related: What is an MCP server?, How to build an MCP server, Playwright MCP server, How to build an AI agent, What is an API key?.
Start for free or see all free tools. We.Inc is free to start, with no card needed. AI building is on paid plans from $20 a month.
We.Inc is an AI-powered website builder you can resell under your own brand. Launch a branded client dashboard, bill on Stripe Connect, and deliver AI-generated websites in minutes. White-label plans start at $99 a month for 25 client sites, with a 7-day free trial and no per-site fees.