Direct answer: Finta's Aurora catalog lists Atlassian Rovo MCP at https://mcp.atlassian.com/v1/mcp/authv2 with dynamic OAuth. Atlassian documents supported Jira, Confluence, Rovo search, fetch, and selected Teamwork Graph tools, governed by OAuth scopes, product permissions, domain controls, and organization policy.
This guide is for teams using Finta as relationship intelligence around a capital, investor, customer, or company-building workflow. Atlassian remains the source system for its records. Aurora can use only the context and actions exposed to the connected account.
How the Atlassian connection works
| Connection detail | Current Finta guidance |
|---|---|
| Classification | Catalog MCP |
| Configured endpoint | https://mcp.atlassian.com/v1/mcp/authv2 |
| Authentication and transport | Provider OAuth through Aurora; Streamable HTTP |
| Source of truth | Atlassian remains authoritative for provider records, permissions, and action results. |
| Human control | Review external communication, record changes, financial actions, publishing, deletion, and other consequential work before execution. |
What you can use it for
- Search and read authorized Jira issues and Confluence content.
- Use Rovo search and fetch tools for source-linked context when available.
- Create or update supported Jira work items after human approval.
- Retrieve Teamwork Graph context only when the beta feature and permissions are available.
- Respect Atlassian domain and IP allowlist controls during connection.
These uses summarize the current provider documentation and Finta catalog purpose. The exact tool inventory varies by provider version, plan, workspace, user permissions, region, and authorization scopes.
Relationship intelligence workflows for Atlassian
Coordinate a technical diligence request
Outcome: Create or update the issue only after the product or security owner approves it.
- Search Jira and Confluence for existing answers and source owners.
- Separate approved documentation from gaps or stale material.
- Prepare a diligence issue with owner, due date, and source links.
- Create or update the issue only after the product or security owner approves it.
Human decision: Do not copy confidential investor questions or sensitive technical details into broadly visible Jira or Confluence spaces.
Prepare a product milestone update
Outcome: Have the owner approve any investor-facing version.
- Find the relevant Jira work and Confluence decision records.
- Distinguish completed work from planned or blocked work.
- Draft a source-linked internal summary with explicit unknowns.
- Have the owner approve any investor-facing version.
Human decision: Jira status alone does not prove deployment, adoption, customer value, or revenue.
How to connect Atlassian to Aurora
- Confirm the organization's Rovo MCP entitlement and admin policy.
- In Aurora, open Apps and select Atlassian.
- Authorize the catalog endpoint and select the intended Atlassian site and identity.
- Review Jira, Confluence, Rovo, domain, and IP allowlist restrictions.
- Run a read-only Jira or Confluence search before any issue write.
Open the official Finta apps directory to confirm the catalog entry before authorizing a provider account.
Permissions and approval boundary
Atlassian access follows OAuth scopes, product permissions, site access, domain controls, and organization policy. Require human approval before issue creation, transitions, comments, assignments, edits, or other writes. Keep diligence and relationship context in appropriately restricted projects and spaces.
Limitations to understand
- Rovo MCP availability, credits, and supported tools can depend on plan and rollout status.
- Teamwork Graph tools are beta and may change.
- Third-party connected data remains subject to its own source permissions.
- The catalog endpoint and auth path must be checked against Atlassian's current setup guidance before publishing exact instructions.
Verification checklist
- Confirm entitlement, endpoint, OAuth flow, Atlassian site, domain policy, and IP allowlist behavior.
- Capture granted scopes and the exact Jira, Confluence, Rovo, and graph tools Aurora discovers.
- Run a safe read-only search in a controlled project or space and retain the receipt.
- Create or edit one test issue only after approval and verify the change and audit history.
- Record plan gates, beta tools, permissions, and verification date before publication.
Verification status: On 2026-08-22, Finta confirmed that this connector appears in the enabled production Aurora catalog and reviewed the configured endpoint, authentication type, and first-party sources listed below. This is not a claim that every provider tool or an authenticated end-to-end action has been tested for every account.
Official provider sources
- Atlassian official MCP documentation (support.atlassian.com)
- Atlassian official MCP documentation 2 (support.atlassian.com)
- Atlassian official MCP documentation 3 (support.atlassian.com)