Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
@@ -0,0 +1,77 @@
export const sectionTitle = 'Common workflows'

import { Tabs, TabItem, Aside } from '@astrojs/starlight/components'

### Get your cloud ID

Most Atlassian Rovo MCP tools require a `cloudId` — the UUID that identifies your Atlassian cloud site. Call `atlassianmcp_getaccessibleatlassianresources` once to retrieve it, then pass the `id` field value in every subsequent tool call.

<Aside type="note" title="Call this tool first">
Run `atlassianmcp_getaccessibleatlassianresources` before calling any Jira or Confluence tool. The response lists every Atlassian site the user has access to. Use the `id` field as `cloudId`.
</Aside>

<Tabs syncKey="tech-stack">
<TabItem label="Node.js">
```typescript
// Step 1 — get the cloud ID
const resources = await actions.executeTool({
connectionName: 'atlassianmcp',
identifier: 'user_123',
toolName: 'atlassianmcp_getaccessibleatlassianresources',
toolInput: {},
});
const cloudId = resources[0].id;

// Step 2 — use cloudId in subsequent calls
const issue = await actions.executeTool({
connectionName: 'atlassianmcp',
identifier: 'user_123',
toolName: 'atlassianmcp_getjiraissue',
toolInput: {
cloudId,
issueIdOrKey: 'KAN-1',
},
});
console.log(issue);
```
</TabItem>
<TabItem label="Python">
```python
# Step 1 — get the cloud ID
resources = actions.execute_tool(
connection_name="atlassianmcp",
identifier="user_123",
tool_name="atlassianmcp_getaccessibleatlassianresources",
tool_input={},
)
cloud_id = resources[0]["id"]

# Step 2 — use cloud_id in subsequent calls
issue = actions.execute_tool(
connection_name="atlassianmcp",
identifier="user_123",
tool_name="atlassianmcp_getjiraissue",
tool_input={
"cloudId": cloud_id,
"issueIdOrKey": "KAN-1",
},
)
print(issue)
```
</TabItem>
</Tabs>

The `getaccessibleatlassianresources` response looks like this:

Comment on lines +64 to +65
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use the exact tool name in the response label.

Line 64 drops the atlassianmcp_ prefix (getaccessibleatlassianresources), which is inconsistent with the callable tool name used elsewhere on the page.

Suggested fix
-The `getaccessibleatlassianresources` response looks like this:
+The `atlassianmcp_getaccessibleatlassianresources` response looks like this:

As per coding guidelines: “For Atlassian MCP, Jira/Confluence tool calls require cloudId. Call atlassianmcp_getaccessibleatlassianresources first...”.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
The `getaccessibleatlassianresources` response looks like this:
The `atlassianmcp_getaccessibleatlassianresources` response looks like this:
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@src/components/templates/agent-connectors/_section-after-setup-atlassianmcp-common-workflows.mdx`
around lines 64 - 65, The response label currently drops the atlassianmcp_
prefix; update the text on the page to use the exact callable tool name
atlassianmcp_getaccessibleatlassianresources everywhere (replace occurrences of
getaccessibleatlassianresources with
atlassianmcp_getaccessibleatlassianresources) so it matches the tool used in
examples and follows the Atlassian MCP guideline about calling
atlassianmcp_getaccessibleatlassianresources first for cloudId retrieval.

```json
[
{
"id": "a4c9b3e2-1234-5678-abcd-ef0123456789",
"name": "My Company",
"url": "https://mycompany.atlassian.net",
"scopes": ["read:jira-work", "write:jira-work", "read:confluence-content.all"]
}
]
```

Use `id` as the `cloudId` parameter. If the user belongs to multiple Atlassian sites, the list contains one entry per site — pick the one matching the target `url`.
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
import { Steps, Aside } from '@astrojs/starlight/components'

Atlassian Rovo MCP uses Dynamic Client Registration (DCR) — no client ID or secret is needed. The only step is registering your Scalekit redirect URI as an allowed domain in Atlassian Administration.

<Steps>
1. ### Copy the redirect URI from Scalekit

In the [Scalekit dashboard](https://app.scalekit.com), go to **AgentKit** > **Connections** > **Create Connection**. Find **Atlassian Rovo MCP** and click **Create**. Copy the redirect URI — it looks like `https://<SCALEKIT_ENVIRONMENT_URL>/sso/v1/oauth/<CONNECTION_ID>/callback`.

![Copy redirect URI from Scalekit dashboard for Atlassian Rovo MCP](@/assets/docs/agent-connectors/atlassianmcp/copy-redirect-uri.png)

2. ### Open the Rovo MCP server settings in Atlassian

- Go to [admin.atlassian.com](https://admin.atlassian.com) and select your organisation.
- In the left sidebar, expand **Rovo** and click **Rovo access**.
- Click **Rovo MCP server** in the submenu.
- Select the **Domains** tab at the top of the page.

<Aside type="note" title="Admin access required">
You must be an Atlassian organisation admin to access these settings. If you don't see **Rovo** in the sidebar, your organisation may not have Rovo enabled.
</Aside>

3. ### Add the redirect URI as a domain

- Under **Your domains**, click **Add domain**.

![Your domains section in Atlassian Rovo MCP server administration](@/assets/docs/agent-connectors/atlassianmcp/add-domain-redirect-uri.png)

- In the **Add domain** dialog, paste the redirect URI from Scalekit into the **Domain** field.
- Accept the terms and click **Add**.

![Add domain dialog in Atlassian Rovo MCP server](@/assets/docs/agent-connectors/atlassianmcp/add-domain-modal.png)

Once added, Scalekit automatically registers the OAuth client via DCR and handles token management for every user who authorizes the connection — no further configuration needed.
</Steps>
5 changes: 4 additions & 1 deletion src/components/templates/agent-connectors/index.ts
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@ export { default as SetupAirtableSection } from './_setup-airtable.mdx'
export { default as SetupApifymcpSection } from './_setup-apifymcp.mdx'
export { default as SetupApolloSection } from './_setup-apollo.mdx'
export { default as SetupAsanaSection } from './_setup-asana.mdx'
export { default as SetupAtlassianmcpSection } from './_setup-atlassianmcp.mdx'
export { default as SetupAttioSection } from './_setup-attio.mdx'
export { default as SetupBigquerySection } from './_setup-bigquery.mdx'
export { default as SetupBigqueryserviceaccountSection } from './_setup-bigqueryserviceaccount.mdx'
Expand Down Expand Up @@ -72,6 +73,7 @@ export { default as ConnectedAccountBigqueryserviceaccountSection } from './_con
export { default as SectionAfterAuthenticationGoogledwdAuth } from './_section-after-authentication-googledwd-auth.mdx'
export { default as SectionAfterSetupAirtableCommonWorkflows } from './_section-after-setup-airtable-common-workflows.mdx'
export { default as SectionAfterSetupApifymcpCommonWorkflows } from './_section-after-setup-apifymcp-common-workflows.mdx'
export { default as SectionAfterSetupAtlassianmcpCommonWorkflows } from './_section-after-setup-atlassianmcp-common-workflows.mdx'
export { default as SectionAfterSetupApolloCommonWorkflows } from './_section-after-setup-apollo-common-workflows.mdx'
export { default as SectionAfterSetupAsanaCommonWorkflows } from './_section-after-setup-asana-common-workflows.mdx'
export { default as SectionAfterSetupAttentionCommonWorkflows } from './_section-after-setup-attention-common-workflows.mdx'
Expand Down Expand Up @@ -103,8 +105,8 @@ export { default as SectionAfterSetupGoogleAdsCommonWorkflows } from './_section
export { default as SectionAfterSetupGooglecalendarCommonWorkflows } from './_section-after-setup-googlecalendar-common-workflows.mdx'
export { default as SectionAfterSetupGoogledocsCommonWorkflows } from './_section-after-setup-googledocs-common-workflows.mdx'
export { default as SectionAfterSetupGoogledriveCommonWorkflows } from './_section-after-setup-googledrive-common-workflows.mdx'
export { default as SectionAfterSetupGoogledwdCommonWorkflows } from './_section-after-setup-googledwd-common-workflows.mdx'
export { default as SectionAfterSetupGoogledwdConnectedAccount } from './_section-after-setup-googledwd-connected-account.mdx'
export { default as SectionBeforeToolListGoogledwdCommonWorkflows } from './_section-before-tool-list-googledwd-common-workflows.mdx'
export { default as SectionAfterSetupGoogleformsCommonWorkflows } from './_section-after-setup-googleforms-common-workflows.mdx'
export { default as SectionAfterSetupGooglemeetCommonWorkflows } from './_section-after-setup-googlemeet-common-workflows.mdx'
export { default as SectionAfterSetupGooglesheetsCommonWorkflows } from './_section-after-setup-googlesheets-common-workflows.mdx'
Expand Down Expand Up @@ -146,6 +148,7 @@ export { default as SectionAfterSetupZendeskCommonWorkflows } from './_section-a
export { default as SectionAfterSetupZoomCommonWorkflows } from './_section-after-setup-zoom-common-workflows.mdx'
export { default as SectionAfterToolListSalesforceMetadataApiSoap } from './_section-after-tool-list-salesforce-metadata-api-soap.mdx'
export { default as SectionBeforeToolListDatadogResourceIds } from './_section-before-tool-list-datadog-resource-ids.mdx'
export { default as SectionBeforeToolListGoogledwdCommonWorkflows } from './_section-before-tool-list-googledwd-common-workflows.mdx'
export { default as SectionBeforeToolListHubspotResourceIds } from './_section-before-tool-list-hubspot-resource-ids.mdx'
export { default as SectionBeforeToolListLinearResourceIds } from './_section-before-tool-list-linear-resource-ids.mdx'
export { default as SectionBeforeToolListMondayResourceIds } from './_section-before-tool-list-monday-resource-ids.mdx'
Expand Down
85 changes: 85 additions & 0 deletions src/content/docs/agentkit/connectors/atlassianmcp.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,85 @@
---
title: 'Atlassian Rovo MCP connector'
tableOfContents: true
description: 'Connect to Atlassian Rovo MCP server to manage Jira issues, Confluence pages, and Compass components directly from your AI workflows.'
sidebar:
label: 'Atlassian Rovo MCP'
overviewTitle: 'Quickstart'
connectorIcon: https://cdn.scalekit.com/sk-connect/assets/provider-icons/atlassian.svg
connectorAuthType: OAuth 2.0
connectorCategories: [project_management, productivity]
tags: [agentkit, connector, atlassian, jira, confluence, compass, project-management, mcp]
head:
- tag: style
content: |
.sl-markdown-content h2 {
font-size: var(--sl-text-xl);
}
.sl-markdown-content h3 {
font-size: var(--sl-text-lg);
}
---

import ToolList from '@/components/ToolList.astro'
import { tools } from '@/data/agent-connectors/atlassianmcp'
import { Steps, Tabs, TabItem } from '@astrojs/starlight/components'
import { AgentKitCredentials } from '@components/templates'
import { SetupAtlassianmcpSection } from '@components/templates'
import { QuickstartGenericOauthSection } from '@components/templates'

<Steps>

1. ### Install the SDK

<Tabs syncKey="tech-stack">
<TabItem label="Node.js">
```bash frame="terminal"
npm install @scalekit-sdk/node
```
</TabItem>
<TabItem label="Python">
```bash frame="terminal"
pip install scalekit
```
</TabItem>
</Tabs>

Full SDK reference: [Node.js](/agentkit/sdks/node/) | [Python](/agentkit/sdks/python/)

2. ### Set your credentials

<AgentKitCredentials />

3. ### Set up the connector

Register your Atlassian Rovo MCP credentials with Scalekit so it handles the token lifecycle. You do this once per environment.

<details>
<summary>Dashboard setup steps</summary>

<SetupAtlassianmcpSection />

</details>

4. ### Authorize and make your first call

<QuickstartGenericOauthSection connector="atlassianmcp" toolName="atlassianmcp_fetch" providerName="Atlassian Rovo MCP" toolInputNode="{ id: 'https://example.com/id' }" toolInputPython='{"id":"https://example.com/id"}' />

</Steps>

## What you can do

Connect this agent connector to let your agent:

- **Manage Jira issues** — create, edit, transition, comment on, and link issues; add worklogs and watchers
- **Search with JQL** — query issues using Jira Query Language with full field and filter support
- **Work with Confluence** — create, update, and retrieve pages; add footer and inline comments
- **Manage Compass components** — create, get, and search services, libraries, and applications; define custom fields and relationships
- **Look up users and resources** — resolve Atlassian account IDs, list accessible cloud sites, and find project metadata
- **Fetch any URL** — retrieve external web content and docs directly from your AI workflow

## Tool list

Use the exact tool names from the **Tool list** below when you call `execute_tool`. If you're not sure which name to use, list the tools available for the current user first.

<ToolList tools={tools} />
Loading