Connect Jira and Confluence (Atlassian Cloud)

Nexatron reads Jira and Confluence through Atlassian's hosted MCP server and answers as the signed-in person: every question runs under that person's own Atlassian login, so Atlassian applies their project permissions, issue security and space restrictions, and Nexatron never sees an issue or page they cannot open themselves. There is no shared service account.

Atlassian Cloud only. Jira or Confluence Server and Data Center are not reachable through Atlassian's hosted MCP server.

Nothing to register. Nexatron registers itself with Atlassian's MCP server automatically. You do not create an app in the Atlassian developer console, and there is no client id or secret to paste.

What you need

• An Atlassian Cloud site with Jira and/or Confluence. People who will ask questions need a licensed Atlassian account on that site.
• A Nexatron workspace admin (the tenant_admin role) to create the connection.

Workspace admin: create the connection

1. In Nexatron, go to Connections → New connection → Business apps → Atlassian (Jira + Confluence).
2. Name it, pick the access level, and save. Questions only is the default. Questions and governed actions lets people create and update Jira issues and Confluence pages through confirmed actions (see Writing back below). Creating the connection signs no one in.

Everyone: connect your own login

1. In Nexatron, open Settings → Connected accounts. Every role can open it.
2. Find the Atlassian connection and choose Connect Atlassian.
3. First screen, from Atlassian's MCP server: approve Nexatron for the apps listed (Jira, Confluence).
4. Second screen, from Atlassian: pick your site and accept. It lists the permissions Nexatron asked for: read permissions, plus update permissions only when your admin set the connection to Questions and governed actions. A question never writes except through an action you confirm first.
5. You are returned to Nexatron and the card shows your Atlassian account.

From then on your questions about Jira and Confluence run under your own login, with the token refreshed automatically. You can Disconnect from the same card at any time.

If you ask a question before connecting, Nexatron tells you so and points you to Connected accounts. Your workspace admin can see who has connected on the connection's page, but never anyone's tokens.

What Nexatron will ask Atlassian

For questions, Nexatron calls a curated read-only set (apart from the governed actions under Writing back) of Atlassian's tools: Rovo search across Jira and Confluence, issue lookup and JQL search, project and issue-type metadata, links and transitions (read), account lookup, Confluence pages, comments, spaces and CQL search. Write tools such as creating or editing issues, adding comments, or updating pages are refused before they are called, and the refusal names the tool. Extending the set is a Nexatron change, never a workspace setting.

Writing back

Unless your admin set the connection to Questions only or switched actions off for the workspace, you can ask Nexatron to create a Jira issue (atlassian.jira.issue.create), comment on one (atlassian.jira.issue.comment), move it through its workflow (atlassian.jira.issue.transition), edit its fields (atlassian.jira.issue.update), or create and update a Confluence page (atlassian.confluence.page.create, atlassian.confluence.page.update), log time on an issue (atlassian.jira.issue.worklog), link two issues (atlassian.jira.issue.link), or comment on a page (atlassian.confluence.page.comment). Each request shows you a card first: what will happen, what else it triggers (watcher notifications, automation rules), and a Confirm and run button. Nothing is written until you confirm, and the write runs as you, with your own Jira and Confluence permissions. If your grant predates the Questions and governed actions setting, Nexatron tells you to reconnect once under Settings → Connected accounts.

Least privilege

Each person's token carries that person's Jira and Confluence permissions, nothing more. Give analytics users browse and view permissions on the projects and spaces they should query; a write action can only do what that person could do in Jira or Confluence directly.

Troubleshooting

Symptom	Cause
"We can't reach Atlassian as you"	You have not connected your login under Settings → Connected accounts
The first screen lists several callback addresses	Nexatron registers one per environment it runs in; that is expected
A tool is refused	It is outside the curated question set (apart from the governed actions); the refusal names it
A question about issues fails with "add a search restriction"	Atlassian refuses unbounded searches; add a project, date or status to the question
Jira or Confluence Server / Data Center	Not reachable; Atlassian Cloud only