Skip to main content
Atlassian Rovo MCP × NGPILOT

Your AI tools, working on Confluence & Jira

Connect Claude Code, Cursor or a Rovo Studio agent and the NGPILOT apps do the work: write Markdown pages, draw Mermaid and Excalidraw diagrams, answer who changed what. 5 MCP servers, 23 tools, all running inside your Atlassian site.

The setup matrix

Five servers, 23 tools

ServerProductToolsConnect URLDocs
Enhanced Markdown for Confluence
Create, read, update and convert Markdown on pages and blog posts.
Confluence4
create-markdown, get-markdown, update-markdown, convert-markdown-blocks
mcp.atlassian.com/forge/6c4adb40-91c3-41db-8804-db25b2998069Docs
Mermaid Plus Diagrams & AI Agent for Confluence
Create, read, update and convert Mermaid diagrams on pages.
Confluence4
create-diagram, get-diagram, update-diagram, convert-diagram
mcp.atlassian.com/forge/0ddaf927-b00c-4186-8b1a-490be0cb7b69Docs
Excalidraw Plus Whiteboards & AI Agent for Confluence
Draw, search, restyle, auto-layout and convert whiteboards — plus a 220+ shape library.
Confluence9
create_excalidraw_diagram, get_excalidraw_diagram, search_excalidraw_diagrams, update_excalidraw_diagram, manage_excalidraw_elements, manage_excalidraw_style, excalidraw_layout, apply_excalidraw_library, convert_excalidraw
mcp.atlassian.com/forge/8730c18b-ea32-4adc-9b58-ddee43f4375dDocs
Mermaid Plus Diagrams & AI Agent for Jira
One diagram per issue, stored on the issue — created and revised by key.
Jira3
create-diagram, get-diagram, update-diagram
mcp.atlassian.com/forge/b1190f13-ccbd-4598-b6a6-fd4276d41594Docs
Issue History Agent for Jira
Field-level history, word-level diffs and point-in-time snapshots for any issue.
Jira3
get-issue-changelog, get-field-diff, get-issue-snapshot
mcp.atlassian.com/forge/6d8c0422-1e39-484b-b647-48b55f621a5dDocs
Connect in three steps

How to connect a client

1. Turn the tools on

External MCP access is off by default. In admin.atlassian.com, open your organization → Apps → Sites → your site → Connected apps, select the app, and switch on its tools. One-time per site; the built-in Rovo agents do not need this step.

2. Register the server

Point your client at the server URL from the table above. For Claude Code:

claude mcp add --transport http enhanced-markdown \
  https://mcp.atlassian.com/forge/6c4adb40-91c3-41db-8804-db25b2998069

Cursor and any other MCP client: add the same URL as a remote (HTTP) MCP server.

3. Authorize yourself

Each user approves their own client through Atlassian OAuth — run /mcp in Claude Code and choose Authenticate. Until then the server shows Needs authentication. Edits made through MCP run with your own permissions.

Good to know: there is no open-page context over MCP — point the client at the page URL or its numeric ID (Confluence) or the issue key (Jira) in your prompt.

Examples

Prompts that work

Enhanced Markdown for Confluence

“Create a page titled "API Style Guide" in our DEV space from this markdown: …”

“Read the markdown on <page URL> and tighten the wording”

“Update the markdown on page 123456789 — replace the "Draft" warning box with a final release note”

Mermaid Plus Diagrams & AI Agent for Confluence

“Create a flowchart of our release process on page 123456789”

“Get the diagram source on <page URL> and hand me the mermaid code”

“Update the diagram on page 123456789 — run Review and Approve in parallel”

Excalidraw Plus Whiteboards & AI Agent for Confluence

“Create a login-screen wireframe board on page 123456789”

“Search our ENG space for whiteboards mentioning "auth" and list them”

“Convert the mermaid block on <page URL> into an editable Excalidraw board”

Mermaid Plus Diagrams & AI Agent for Jira

“Create a deployment flowchart on issue KRA-482”

“Show me the diagram source on KRA-482”

“Update the diagram on KRA-482 — add a rollback step after Deploy”

Issue History Agent for Jira

“Who changed what on KRA-914 last week? Field-level diff.”

“Get the full changelog of KRA-914”

“Show KRA-914 as it looked before the status change on Monday”

Where your data lives

Inside your Atlassian site

No NGPILOT servers in the middle

The MCP servers are part of the Forge apps themselves. Requests go from your AI client to Atlassian and back — we have no servers, and nothing passes through our infrastructure.

Your token, your permissions

Every client authorizes itself with your own Atlassian account. The tools can only reach what you can reach, and every edit is attributed to you.

Off until an admin says otherwise

Third-party MCP access is disabled by default, per site. A site or organization admin turns the tools on in admin.atlassian.com before any client can see them.

Revoke any time

The OAuth connection is per user and per client. Remove it from your Atlassian account settings and the client loses access immediately.