Jira & Confluence MCP Servers
The platform provides MCP server integrations for both Jira and Confluence. Since both services are part of the Atlassian platform, they share the same OAuth app and credentials — you configure authentication once and can enable either or both services.
Jira
Capabilities
| Tool | What It Does |
|---|---|
| Search issues | Search for issues using JQL (Jira Query Language) |
| Get issue | Retrieve details about a specific issue |
| Create issue | Create a new issue in a project |
| Update issue | Modify fields on an existing issue |
| Add comment | Post a comment on an issue |
| Transition issue | Move an issue to a different status |
| List projects | List available Jira projects |
| Get project | Retrieve details about a specific project |
Confluence
Capabilities
| Tool | What It Does |
|---|---|
| Search content | Search pages and blog posts using CQL (Confluence Query Language) |
| Get page | Retrieve the full content of a page |
| Create page | Create a new page in a space |
| Update page | Edit the content of an existing page |
| Add comment | Post a comment on a page |
| List spaces | List available Confluence spaces |
| Get space | Retrieve details about a specific space |
OAuth Setup
Both Jira and Confluence use the same Atlassian OAuth app. You create one app and use it for both services.
Step 1: Create an Atlassian OAuth App
- Go to the Atlassian Developer Console and sign in.
- Click Create > OAuth 2.0 integration.
- Enter a name (for example, "Devs AI MCP") and agree to the developer terms.
- Click Create.
Step 2: Configure the Callback URL
- In the left sidebar, go to Authorization.
- Under OAuth 2.0 (3LO), click Configure.
- Add the redirect URL(s) provided by your Devs.ai platform administrator.
Step 3: Add Permissions and Scopes
- In the left sidebar, go to Permissions.
- Click Add next to Jira API and select the following scopes:
| Scope | Description |
|---|---|
read:jira-work | Read project and issue data, search for issues |
write:jira-work | Create and edit issues, post comments, manage worklogs |
read:jira-user | View user information (usernames, emails, avatars) |
- Click Add next to Confluence API and select the following scopes:
| Scope | Description |
|---|---|
read:confluence-content.all | Read all page and blog content, including body text |
write:confluence-content | Create and update pages, blogs, and comments |
read:confluence-space.summary | View space information and metadata |
search:confluence | Search across Confluence content |
read:confluence-user | View user profiles |
📝 Note: You can include scopes for both Jira and Confluence in a single OAuth app. If you only need one service, you only need to add the scopes for that service.
Step 4: Get Your Credentials
- In the left sidebar, go to Settings.
- Copy the Client ID and Secret (click Show to reveal).
Step 5: Configure in Devs.ai
- Navigate to Organization > Connectors in Devs.ai.
- Find the Jira or Confluence template and click Enable.
- Select OAuth as the authentication type.
- Enter your Client ID and Client Secret from Step 4.
- Select the tools you want to make available.
- Click Save.
You can enable Jira and Confluence separately. Both use the same Client ID and Client Secret.
How Atlassian Cloud Authentication Works
Atlassian Cloud APIs use a per-tenant Cloud ID in the API URL. After a user authorizes access, the platform automatically:
- Retrieves the user's accessible Atlassian sites.
- Determines the correct Cloud ID for the user's site.
- Uses the correct base URL for all API requests (for example,
https://api.atlassian.com/ex/jira/{cloudId}/rest/api/3).
This is handled transparently — you do not need to configure the Cloud ID manually.
OAuth Configuration Reference
| Field | Value |
|---|---|
| Authorization URL | https://auth.atlassian.com/authorize |
| Token URL | https://auth.atlassian.com/oauth/token |
| Scopes Parameter Name | scope (space-separated) |
| Additional Parameters | prompt=consent, response_type=code |