Rovo Agent Connector (EAP)

The rovo:agentConnector module allows you to integrate remote AI agents hosted on external infrastructure into Jira. Once a remote agent is registered, users can interact with them in a similar manner to other users and Rovo agents: assigning them work items, @mentioning them in comments, and chatting with them via the Rovo Chat panel.

Use this module to integrate Jira with AI agents residing outside of the Atlassian platform (such as GitHub Copilot, Cursor Background Agents, or Box AI Agents).

Requirement: Agent2Agent protocol server

Remote agents must implement an Agent2Agent (A2A) protocol server to communicate with Jira. The A2A protocol is an open standard that enables AI agents to communicate with each other, regardless of the underlying framework or vendor.

For more information, see Getting Started.

Jira communicates with remote agents via the JSON-RPC 2.0 protocol. Your remote service must expose an endpoint that accepts JSON-RPC requests from Jira and returns responses according to the A2A protocol specification.

EAP limitations

During the EAP, apps using Rovo Agent Connector:

• Can't be deployed to the production and staging environments.
• Can't be distributed or listed on the Atlassian Marketplace.

Manifest structure

1
2
modules {}
└─ rovo:agentConnector []
   ├─ key (string) [Mandatory]
   ├─ name (string) [Mandatory]
   ├─ description (string) [Optional]
   ├─ icon (string) [Optional]
   ├─ conversationStarters [] [Optional]
   │  └─ conversationStarter (string)
   ├─ productContexts [] [Mandatory]
   │  └─ product (string)
   └─ protocols [] [Mandatory]
      └─ agent2Agent
         └─ jsonRpcTransport
            ├─ streaming (boolean)
            └─ endpoint (string)

remotes []
└─ key (string) [Mandatory]
└─ baseUrl (string) [Mandatory]

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

permissions []
└─ scopes []
  └─ scope (string) [Mandatory]

In this structure:

• The rovo:agentConnector module defines a remote agent with metadata and communication protocols.
• The endpoint property references a separately defined endpoint module, which specifies the route Jira uses to communicate with your remote agent via JSON-RPC.
• The remotes configuration identifies the domain of your remote service and enables authentication tokens to be passed to your service.
• The resources module provides static assets like the agent icon.
• The productContexts property specifies which Atlassian products the agent operates in. Only jira is supported during the EAP.
• The permissions.scopes array declares the OAuth scopes your app requires. The read:jira-work scope is required for the agent to function correctly.

Properties

A2A Protocols

Transport properties

Related modules

The rovo:agentConnector module works together with other manifest configurations to enable remote agent integration:

Manifest example

The following example manifest file defines an rovo:agentConnector that connects to your remotely hosted agent:

1
2
modules:
  rovo:agentConnector:
    - key: your-awesome-agent
      name: Your Awesome Agent
      description: An awesome agent that you built
      icon: resource:agent-resources;icons/your-agent.svg
      productContexts:
        - jira
      protocols:
        agent2Agent:
          jsonRpcTransport:
            endpoint: a2a-json-rpc-endpoint
            streaming: true
  endpoint:
    - key: a2a-json-rpc-endpoint
      remote: agent-remote
      route:
        path: /a2a/json-rpc
remotes:
  - key: agent-remote
    baseUrl: https://youragent.com
    operations:
      - fetch
      - compute
      - other
resources:
  - key: agent-resources
    path: static/hello-world/build
permissions:
  scopes:
    - read:jira-work