Mermaid Plus for Jira now ships a Rovo AI agent
Six weeks ago Mermaid Plus for Confluence became an AI-agent app — a Rovo agent and an MCP server that read and edit the diagrams living in your wiki. Since then, the question we kept hearing from Jira teams was the same one: our issues are where the design decisions happen — when does the agent come here?
Now. Mermaid Plus Diagrams & AI Agent for Jira ships the same agent architecture, pointed at the place Jira work actually lives: the issue.
What the agent can do on an issue
Jira issues accumulate exactly the content diagrams are good at — architecture sketches attached to epics, workflow flowcharts on process tickets, decision trees on design proposals. Until now, drawing one meant opening the panel editor yourself. Three tools change that:
| Tool | What it does |
|---|---|
create-diagram | Attaches a rendered Mermaid diagram to an issue |
get-diagram | Reads the diagram source and type back |
update-diagram | Replaces the source in place, keeping your theme and color settings |
The agent edits the same issue property your team edits by hand. Nothing is forked into a side store: an agent-written diagram shows up in the issue panel immediately, and the next person who opens the editor sees exactly what the agent wrote.
Two refusal rules do most of the safety work. One diagram per issue — create-diagram refuses when one exists and points at update-diagram, so the agent never stacks duplicates. And no uninvited writes — when there's no diagram to read or update, the agent stops and asks instead of "helpfully" attaching something you didn't ask for. A wrong-issue or wrong-intent write is the one failure this feature must never have.
Three ways to use it
1. From an issue (already live). Start a Rovo chat on the issue — the key comes from context automatically. The highest-leverage prompt is the one only an issue-aware agent can do: "diagram this issue" — the agent reads the summary and description and drafts the diagram from the work item itself.
2. In agents you build in Rovo Studio. Add the three Mermaid Plus tools to any Rovo Studio agent, next to tools from your other connected apps. An agent that triages incoming bugs and keeps each one's architecture sketch current is a configuration exercise, not an integration project.
3. In any MCP client. Claude Code, Cursor, or anything that speaks MCP can connect to:
https://mcp.atlassian.com/forge/b1190f13-ccbd-4598-b6a6-fd4276d41594
Exposure is admin-controlled per site: external access is off by default, and a site admin flips it on under Apps → Sites → your site → Connected apps → Mermaid Plus → Tools in Atlassian Administration. Users then approve their own connection through an OAuth 2.1 consent screen. (The built-in Rovo agent needs none of this — it's live the moment the app is installed.)
Connecting Claude Code, concretely:
claude mcp add --scope user --transport http mermaid-plus-jira \
https://mcp.atlassian.com/forge/b1190f13-ccbd-4598-b6a6-fd4276d41594
Then start claude, run /mcp, select mermaid-plus-jira → Authenticate, approve the consent screen, and try:
Read the diagram on DEV-123 and update it to cover the new retry path
Over MCP there is no open issue, so you pass the key (DEV-123 from the issue URL) explicitly — the tools refuse to guess, and missing keys come back as an ask-the-user error.
Permissions travel with the person, not the bot
Every call runs on the invoking user's own Jira token. Reading needs Browse on the issue; changing the diagram needs Edit Issues. That's not a policy statement, it's the architecture: the app has no as-app write fallback in the agent path, so "the agent did it" can never exceed "I did it." Installation, billing, and data residency are unchanged — the agent is a capability of the Forge app already on your site, not a new vendor trust decision.
Naming note
The app is now Mermaid Plus Diagrams & AI Agent for Jira — the listing name catches up with what it does, matching the Confluence sibling. Same add-on key, same panel, same pricing; existing installs and links are unaffected.
Both apps are live on the Atlassian Marketplace: Mermaid Plus for Jira and Mermaid Plus for Confluence. The full walkthrough — admin setup, Claude Code, Rovo Studio — is in the user guide.
Try Mermaid Plus Diagrams & AI Agent for Confluence
All 30 Mermaid diagram types plus a Rovo AI agent, with live preview and one-click templates — free for up to 10 users.
Get it on the Atlassian Marketplace