-
Notifications
You must be signed in to change notification settings - Fork 10
Add Atlassian Rovo MCP connector docs #705
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Pranesh-Raghu
wants to merge
7
commits into
main
Choose a base branch
from
preview/atlassianmcp-connector
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
174a8b9
add Atlassian Rovo MCP connector docs
Pranesh-Raghu b4e35ec
add Atlassian Rovo MCP setup guide with domain configuration steps an…
Pranesh-Raghu 8e61b15
fix: simplify Atlassian Rovo MCP setup guide for DCR flow, update scr…
Pranesh-Raghu 94ca1e7
resolve CodeRabbit comments: fix wrong-context param descriptions, ca…
Pranesh-Raghu 5d16087
resolve CodeRabbit: fix cross-contaminated param descriptions, clarif…
Pranesh-Raghu 587d6f0
sync connector docs: add new HubSpot engagement tools, re-apply atlas…
Pranesh-Raghu 58dbae1
Revert "sync connector docs: add new HubSpot engagement tools, re-app…
Pranesh-Raghu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+242 KB
src/assets/docs/agent-connectors/atlassianmcp/add-domain-redirect-uri.png
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.
77 changes: 77 additions & 0 deletions
77
...mplates/agent-connectors/_section-after-setup-atlassianmcp-common-workflows.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 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: | ||
|
|
||
| ```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`. | ||
35 changes: 35 additions & 0 deletions
35
src/components/templates/agent-connectors/_setup-atlassianmcp.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 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`. | ||
|
|
||
|  | ||
|
|
||
| 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**. | ||
|
|
||
|  | ||
|
|
||
| - In the **Add domain** dialog, paste the redirect URI from Scalekit into the **Domain** field. | ||
| - Accept the terms and click **Add**. | ||
|
|
||
|  | ||
|
|
||
| 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> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 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} /> |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
As per coding guidelines: “For Atlassian MCP, Jira/Confluence tool calls require
cloudId. Callatlassianmcp_getaccessibleatlassianresourcesfirst...”.📝 Committable suggestion
🤖 Prompt for AI Agents