Rovo MCP (Preview)

The rovo:mcp module lets you expose actions as tools that agents can invoke. Tools are available to custom agents in Rovo Studio, and can also be connected to third-party, MCP-compatible AI clients (Preview). An app can have at most one rovo:mcp module.

Data access

App-based tools can access only the data in the workspace where the app is installed. For example, a Confluence page at yourtenant.atlassian.net that describes your team's CI/CD process is not automatically accessible to an app installed in Jira at yourtenant.atlassian.net.

To enable your tools to access data from multiple Atlassian apps, configure your app to support multiple Atlassian apps. See App compatibility.

When multiple products have different versions of the same app installed, the exposed tools reflect those from the latest app version.

Manifest structure

1
2
3
4
5
6
7
8
9
10
11
modules {}
└─ rovo:mcp []
   ├─ key (string) [Mandatory]
   ├─ name (string) [Mandatory]
   ├─ tools [] [Mandatory]
   │  └─ action (string)

resources []
└─ key (string) [Mandatory]
└─ path (string) [Mandatory]

In this structure:

• The rovo:mcp array includes properties such as key, name, and tools.
• The resources array includes properties key and path.

Properties

Manifest example

Here is an example manifest file that exposes tools for a timesheet app:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
modules:
  rovo:mcp:
    - key: timesheet-mcp
      name: "Timesheet MCP"
      tools:
        - fetch-timesheet-by-date
        - update-timesheet
  action:
    - key: fetch-timesheet-by-date
      name: Fetch timesheet by date
      function: getTimesheetByDate
      actionVerb: GET
      description: |
        Retrieve a user's timesheet based on a date
      inputs:
        timesheetDate:
          title: Timesheet Date
          type: string
          required: true
          description: "The date that the user wants a timesheet for"
    - key: update-timesheet
      name: Update timesheet
      function: updateTimesheet
      actionVerb: UPDATE
      description: |
        Update a user's timesheet entry for a specific date
      inputs:
        timesheetDate:
          title: Timesheet Date
          type: string
          required: true
          description: "The date of the timesheet entry to update"
        hoursWorked:
          title: Hours Worked
          type: number
          required: true
          description: "The number of hours worked to record for the given date"
        projectKey:
          title: Project Key
          type: string
          required: false
          description: "The project or task the hours are attributed to"
        notes:
          title: Notes
          type: string
          required: false
          description: "Optional notes or comments about the timesheet entry"
  function:
    - key: getTimesheetByDate
      handler: index.getTimesheetByDate
    - key: updateTimesheet
      handler: index.updateTimesheet

Tutorials

Hands-on, step-by-step guides for building with the rovo:mcp module:

Related manifest configurations

The rovo:mcp module integrates with other manifest configurations to expose tools in Rovo Studio.

Connect tools to third-party AI clients (Preview)

In addition to custom agents in Rovo Studio, you can connect the tools exposed by your rovo:mcp module to any third-party, MCP-compatible AI client.

External MCP exposure is disabled by default. Before a client can connect, a site or org admin must enable it from Apps > Sites > your site > Connected apps in Atlassian Administration: select your Forge app (the one that declares a rovo:mcp module), open its app details, and turn on the tools you want to expose. This is set per app installation (per site). For full instructions, see Configure tools for an external MCP server.

Each installed app exposes its tools at the following endpoint:

1
2
https://mcp.atlassian.com/forge/<appId>

Where <appId> is the UUID portion of your Forge app ID from app.id in manifest.yml (the part after ari:cloud:ecosystem::app/).

Add this URL to your client's remote MCP server configuration. When the client connects, it opens an OAuth 2.1 consent screen where the user selects the site to connect to (limited to sites where the app is installed and exposure is enabled), reviews the app's scopes and tools, and approves access. Once connected, the client can invoke any of the tools listed in your rovo:mcp module's tools property, subject to the invoking user's own permissions on that site.

For step-by-step instructions, see Build a Rovo MCP hello world app.

Related links

• What is Rovo Studio?