Contents

Jira

Jira shares the same connection as Confluence. Tato can read issues and sprints, create issues, update status, and add comments.

Setup: An Atlassian admin approves Tato once, then a Tato admin adds Atlassian as a connector. Each person then connects their own account from Tato chat.

Connect Jira and Confluence

Before Jira and Confluence can connect, an Atlassian admin has to add Tato's OAuth callback URL in Atlassian. Atlassian calls this adding a domain. You only do this once for your organization.

Copy Tato's OAuth callback URL

  1. Open MCP connectors in your organization settings. Press Cmd+K (Ctrl+K on Windows) and search for MCP connectors.
  2. Copy the OAuth callback URL.

Tato's MCP connectors settings page with the OAuth callback URL copied to the clipboard

Add it in Atlassian

  1. Go to admin.atlassian.com and open the Rovo MCP server page.
  2. Under Your domains, press Add domain.

Atlassian's Rovo MCP server admin page showing the Domains tab and the Add domain button

  1. Paste the OAuth callback URL you copied from Tato, then press Add.

Atlassian's Add domain dialog with Tato's OAuth callback URL pasted in

Finish the connection in Tato

Go back to MCP connectors in Tato and follow Connect your apps to Tato. Use this MCP server URL:

https://mcp.atlassian.com/v1/mcp/authv2

Jira and Confluence share this one connection, so you only add it once.

What you can do

For the full list of actions, see Atlassian's Rovo MCP server documentation.

Paired with a meeting, this becomes more than lookup. For example: ask Tato to pull every open Jira issue for a project, check it against what came up in a meeting, and update any issue whose status or details no longer match what was just discussed.

  • File a ticket the moment Tato flags a bug or risk in a meeting recap.
  • Ask Tato to move a ticket to "in progress" or add a comment with the latest update.

Questions? Reach out at support@tato.co.