Calling a Rovo Agent from an External Custom Agent

[Giuseppe Torraco]

Is it possible to invoke or orchestrate a Rovo agent from an external agent developed in VS Code?
Specifically, I’d like to understand whether there is a supported way to enable communication between a custom, locally developed agent and an existing Rovo agent—such as through APIs, webhooks, or other endpoints exposed by the platform.

What is the recommended approach or the reference documentation to enable this type of integration?

[Anthony Morais]

Hi @Giuseppe Torraco 

No, at the moment there isn’t a supported way to call or orchestrate a Rovo Agent from something running outside the Atlassian platform (like a custom agent in VS Code, a CLI tool, or any standalone app).

Right now, Rovo Agents live entirely inside the Atlassian ecosystem, and they don’t expose APIs, webhooks, or any external endpoints that an outside agent could use to “trigger” or hand off work to them. So in practice:

You can build your own external agent.
You can integrate that external agent with Jira/Confluence via Atlassian’s public APIs.

But you cannot trigger a Rovo Agent or pass instructions to it programmatically from outside Atlassian.
You can integrate it with Jira or Confluence using the regular public APIs.

But you can’t programmatically invoke a Rovo Agent from outside Atlassian.

At the moment, all the orchestration for Rovo Agents happens internally, and they behave like native smart assistants within the platform.

If Atlassian eventually opens up a way to chain or call Rovo Agents from external systems whether via API, events, or some integration layer—it will show up in the developer docs first. But as of today, that capability doesn’t exist.

I hope this simple contribution helps!

[Giuseppe Torraco]

I saw that the Rovo MCP Server is now available in beta.

I would like to know if it can be used to orchestrate extarnal agents or programs together with Rovo agents.

Has anyone tried it and can share their experience?