Add Guide: Atlassian

[svadrutk]

https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/

[walker-tx]

Resolved as atlassian (Atlassian), persona it-admin.

Notes handed to the pipeline:

Draft a guide for the Atlassian Rovo remote MCP server. Docs: https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/

Starting draft-guide…

[walker-tx]

Pipeline review (atlassian)

Outcome: Reviewers passed after 3 round(s). Still skim the open questions below before merging.

Draft PR: #136

Open questions (3)

Research could not prove these from public docs. Check the boxes by replying with answers, or say “unknown / omit”. Silence + an existing hedge in the guide usually means omit / keep hedge — not a console capture.

• Does the Speakeasy MCP Catalog contain an exact Atlassian Rovo MCP Server entry? The supplied catalog lookup was ambiguous, so both add-server paths must remain conditional.
• What exact Speakeasy OAuth redirect domain must an Atlassian organization admin allow for this DCR connection, and what hosted outbound IP ranges must be added when the organization enforces Atlassian IP allowlists? These values are not present in Atlassian's public docs or the canonical Speakeasy setup source.
• If User Installed Apps is blocked, what exact current Atlassian Administration clicks install or approve the Atlassian MCP app? The MCP client page states that a site admin might need to install it but delegates the procedure to a separate app-policy guide rather than documenting the complete path.

Optional nits (1)

• Opening prerequisites and “If your organization uses strict egress filtering”: The opening conditional directs readers to Atlassian Administration even when the only applicable restriction is network egress, but the egress control is not identified as an Atlassian Administration setting. → Limit the Atlassian Administration direction to OAuth-domain, IP-allowlist, and app-policy checks, and tell readers to ask their network or security owner to allow *.atlassian.net when egress filtering applies.

How to retry

1. Reply on this issue using the Decision N: … lines above (render fixes: apply / override; scope gaps: verified / drop / hedge) and answer open questions.
2. Re-add the guide:draft label. Distill reads the issue body and comments into pipeline notes.
3. If a factory draft PR already exists (guide/issue-<N>-*), the next run resumes on that branch and revises prior research/setup instead of starting blank. Late setup-file fidelity misses get one automatic salvage revise at finalization before surfacing here.

Source: run-record.json

[svadrutk]

1. it does but atm catalog is deprecated b/c they use the old protocol (external MCP) and the plan is to migrate all of them over to remote MCP
2. https://app.getgram.ai/mcp/remote_login_callback
3. no idea

[walker-tx]

Resuming on existing factory PR: #136

Resolved as atlassian (Atlassian), persona it-admin.
Prior guides/atlassian/ stays on the branch — research/draft will revise from those artifacts (lock skips when inputs match).

Notes handed to the pipeline:

Draft for the Atlassian Rovo remote MCP server. Docs: https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/ The catalog entry exists but is deprecated because it uses the old external MCP protocol; favor the remote MCP path and keep catalog instructions conditional. Speakeasy OAuth redirect URL: https://app.getgram.ai/mcp/remote_login_callback. Exact hosted outbound IP ranges are unknown; omit or hedge. Exact admin approval/install clicks when User Installed Apps is blocked are unknown; omit or hedge. For strict egress filtering, direct readers to their network/security owner to allow *.atlassian.net; reserve Atlassian Administration guidance for OAuth-domain, IP-allowlist, and app-policy checks.

Starting draft-guide…

[walker-tx]

Pipeline review (atlassian)

Outcome: Reviewers passed after 2 round(s). Still skim the open questions below before merging.

Draft PR: #136

Open questions (4)

Research could not prove these from public docs. Check the boxes by replying with answers, or say “unknown / omit”. Silence + an existing hedge in the guide usually means omit / keep hedge — not a console capture.

• Does the Speakeasy MCP Catalog contain an exact, current Atlassian Rovo remote MCP Server entry in addition to the deprecated old external-protocol entry?
• After selecting Configure Manually, does the discovered Atlassian issuer remain populated in Issuer URL?
• What stable hosted outbound IP ranges, if any, are available when an organization enforces Atlassian IP allowlists?
• When User Installed Apps is blocked, what exact current Atlassian Administration path approves or installs the Atlassian MCP app?

How to retry

1. Reply on this issue using the Decision N: … lines above (render fixes: apply / override; scope gaps: verified / drop / hedge) and answer open questions.
2. Re-add the guide:draft label. Distill reads the issue body and comments into pipeline notes.
3. If a factory draft PR already exists (guide/issue-<N>-*), the next run resumes on that branch and revises prior research/setup instead of starting blank. Late setup-file fidelity misses get one automatic salvage revise at finalization before surfacing here.

Source: run-record.json