You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: guides/atlassian/external.md
+18-9Lines changed: 18 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,34 +6,43 @@ setup_version: 1
6
6
7
7
You need an Atlassian Cloud site with Jira, Confluence, and/or Compass, and the connecting Atlassian account must have access to the intended site and apps. Use a modern browser. Atlassian documents no paid-plan requirement for the MCP Server.
8
8
9
-
You need no Atlassian-side configuration unless your organization restricts OAuth client domains, IP addresses, third-party apps, or network egress. If it does, sign in to Atlassian Administration with an organization-admin account and complete the applicable checks below.
9
+
You need no Atlassian-side configuration unless your organization restricts OAuth client domains, IP addresses, third-party apps, or network egress. For OAuth-domain or IP-allowlist restrictions, sign in to Atlassian Administration with an organization-admin account and complete the applicable checks below. If **User Installed Apps** is blocked, ask a site admin for help. For strict egress filtering, ask your network/security owner to allow the required Atlassian domain.
10
10
11
11
### Allow the Speakeasy OAuth domain {#allow-speakeasy-domain}
12
12
13
13
1. Open [admin.atlassian.com](https://admin.atlassian.com/).
14
14
2. If more than one organization is shown, select the organization you want to connect.
15
15
3. Select **Rovo**.
16
16
4. Select **Rovo MCP server**.
17
-
5. Obtain the exact OAuth redirect domain from your Speakeasy deployment owner.
18
-
6. Check whether that domain is already covered by the allowed domains.
19
-
7. If it is not covered, select **Add domain**.
20
-
8. If it is not covered, add the trusted redirect domain with its protocol and valid host. Use HTTPS for the hosted client.
21
-
9. If it is not covered, use the submission control shown in the console.
17
+
5. Check whether the allowed domains cover this hosted OAuth callback:
18
+
19
+
```
20
+
https://app.getgram.ai/mcp/remote_login_callback
21
+
```
22
+
23
+
6. If it is not covered, select **Add domain**.
24
+
7. Enter this exact custom domain pattern:
25
+
26
+
```
27
+
https://app.getgram.ai/mcp/remote_login_callback
28
+
```
29
+
30
+
8. Use the submission control shown in the console.
1. Ask your Speakeasy deployment owner for the connection's source IP addresses or CIDR blocks.
28
-
2.Return to your organization in [admin.atlassian.com](https://admin.atlassian.com/).
36
+
1. Ask your network/security owner whether hosted Speakeasy traffic has stable outbound IP addresses or CIDR blocks that your organization can allow. Do not guess these ranges.
37
+
2.If your network/security owner supplies ranges, return to your organization in [admin.atlassian.com](https://admin.atlassian.com/).
29
38
3. Select **Security**.
30
39
4. Select **IP allowlists**.
31
40
5. Open the applicable allowlist, or select **Create IP allowlist**.
32
41
6. Enter a name and the source IP addresses or CIDR blocks in the fields shown.
33
42
7. Select the Atlassian sites and apps to which the allowlist applies.
34
43
8. Use the submission control shown in the console.
35
44
36
-
If your organization uses strict egress filtering, allow the following domain so interactive Jira and Confluence widgets can render:
45
+
If your organization uses strict egress filtering, ask your network/security owner to allow the following domain in your organization's network controls so interactive Jira and Confluence widgets can render:
0 commit comments