Tools
Atlassian
Read and write Jira issues and Confluence pages, from Claude or ChatGPT via Tulina's MCP server, on top of Atlassian's own OAuth consent screen.
Official site: atlassian.com
What it does
- Read and write Jira issues
- Read and write Confluence pages
Access runs through Atlassian's own OAuth, so a user grants exactly what a workspace asks for. A federated connection like this puts the vendor's own consent screen between the model and the account, on top of whatever a workspace sets.
How do you connect Atlassian to Claude and ChatGPT?
Through Tulina's MCP server, layered on top of Atlassian's own OAuth consent screen — a workspace grants exactly what it wants seen. Ask for Jira issues or Confluence pages, read or write either, in the same chat as the ticket update or doc edit it triggers, whether that chat is Claude or ChatGPT.
Why through Tulina
Most systems now publish their own way for a model to reach them, and that is a good thing — it is what Tulina connects to. The connection was never the hard part. Deciding who may use it, what it is allowed to return, and what the model knows before it asks: that is.
The keys stay in one place
Connect Atlassian once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that — so nobody is blocked and nobody is handed more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
Roles decide who can reach Atlassian at all. Beyond that, a policy on the connector itself decides what comes back: fields dropped, identifiers masked or hashed, people pseudonymised. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
Runs are logged for the organisation — what was called, by whom, when. That is what makes an automated action reviewable after the fact, and what a security review asks for first.
The run starts knowing your company
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Atlassian returns something usable instead of something generic.
Processes that run on Atlassian
None published yet.