Atlassian

Connecting Atlassian to NeuBird lets you track issues and project activities in real time, including issue statuses, project progress, and sprint metrics. You will need an Atlassian API Token and your Atlassian Instance URL.

Enabling the Atlassian Rovo MCP Server for NeuBird Access

Note

These steps require an Atlassian Organization Admin to complete:

1. Go to admin.atlassian.com and select your organization.
2. In the left sidebar, navigate to Rovo → Rovo MCP server.
3. On the Rovo MCP server page, toggle on API token under Authentication methods. This allows service-based (non-interactive) access to the MCP server.
4. Review the scopes granted to the MCP server. NeuBird only requires read and search access — the write scopes below are optional and only needed if you want NeuBird to create or update issues, alerts, and pull requests. Granting admin access is not required; the granular scopes below are sufficient.

Required scopes (read-only)

NeuBird needs the following read and search scopes to investigate Jira, Confluence, Bitbucket, Compass, and Jira Service Management resources:

Read

read:all:twg
read:3p-data:mcp
read:comment:confluence
read:account
read:hierarchical-content:confluence
read:confluence:mcp
read:home:mcp
read:incident:jira-service-management
read:focus:mcp
read:component:compass
read:confluence:agent-interface
read:confluence-user
read:page:confluence
read:jira-user
read:repository:bitbucket
read:loom:mcp
read:ops-alert:jira-service-management
read:jira:agent-interface
read:pullrequest:bitbucket
read:jira-work
read:pipeline:bitbucket
read:ops-config:jira-service-management
read:me
read:space:confluence
read:user:bitbucket
read:scorecard:compass
read:workspace:bitbucket
read:servicedesk-request
read:whiteboard:confluence
read:talent:mcp

Search

search:rovo:mcp
search:confluence:agent-interface
search:jira:agent-interface
search:confluence

View

view:team:teams

Optional scopes (write)

Grant these only if you want NeuBird to take write actions (for example, opening Jira issues or pull requests). They are not required for read-only investigations:

write:incident:jira-service-management
write:repository:bitbucket
write:jira-work
write:pullrequest:bitbucket
write:ops-alert:jira-service-management
write:jira:agent-interface

Once the admin has enabled API token auth, login with any user (or a NeuBird specific user) with access to the resources that are needed for investigation:

Create an API Token

This demo shows how to create an API token and enable the Atlassian Rovo MCP Server. Access security settings to begin. Create and manage API tokens by selecting the option to create an API token with scopes. Enter a descriptive token name in the Name field. Proceed to scope selection and select Rovo MCP to grant API access. Review the token configuration and confirm settings. Generate the secure API token by clicking Create token to complete the setup process.

1. Navigate to the API token page: Log into your Atlassian account and go to the API tokens page.

   

   Click Create API Token.

2. Name your token: Provide a descriptive name for the token to identify it later.

   

   Click Create.

3. Copy the API token: Once generated, click Copy to save the token.

   

   Store this token securely — it will not be displayed again.

4. Retrieve your Instance URL: Open your Atlassian instance in your browser (e.g., https://yourcompany.atlassian.net).

   

   Copy this URL; it is required for the connection.

Connection Fields

Field	Required	Description
Name	Yes	A descriptive name for this connection
Description	No	An overview of what this connection is used for
API Token	Yes	The API token generated from the Atlassian API tokens page
Instance URL	Yes	Your Atlassian instance URL (e.g., https://yourcompany.atlassian.net)

---

For general instructions on creating and managing connections, see the Connections Overview.