Skip to main content
What you’ll get: ewake can search your Jira issues and read their details and comments during an investigation, surfacing the in-progress or recently-changed work that might explain unexpected behaviour, directly in the incident channel. Connect over Atlassian Rovo MCP and ewake also reads your Confluence pages and searches both semantically.

​
Choose how to connect

ewake speaks to Jira over two transports. You connect the same way for both — paste a Site URL, an account email, and an API token — and ewake detects which transport your token opens. What changes is the token you create, and how much ewake can reach.

Atlassian Rovo MCP

Recommended. A scoped Rovo token unlocks Jira issues, Confluence pages, and semantic search across both. Best coverage during investigations.

REST API

A classic API token reads Jira issues and projects only. Simplest to create — nothing to scope, no admin step.

​
Prerequisites

  • An Atlassian account with access to your Jira workspace
  • Permission to create API tokens in Atlassian
  • For Rovo MCP: an Atlassian organisation admin who can enable Rovo MCP API token authentication (one-time, org-wide)
  • A dedicated service account is recommended, so access doesn’t depend on one person

​
Configuration

1

Enable Rovo MCP API token authentication

An organisation admin enables Rovo MCP API token authentication for your Atlassian organisation. This is a one-time, org-wide setting — without it, scoped tokens cannot open Rovo MCP.
2

Create a scoped API token

Go to id.atlassian.com/manage-profile/security/api-tokens → Create API token with scopes, then work through the wizard in order:1. Name and expiry. Give the token a name (e.g. ewake) and set an expiration date — pick the longest Atlassian allows (no more than 366 days).2. Select the app: Rovo MCP V2. Choose Rovo MCP V2 — not the plain Rovo MCP. A token scoped to the older app cannot open ewake’s Rovo MCP connection.3. Select the scopes. Tick at least these three (all in the :agent-interface group):Create the token and copy it immediately.
The step to get right is Select the app: it must be Rovo MCP V2, not Rovo MCP.
Copy the token now, Atlassian will not show it again after closing the modal.
3

Note your Jira site URL

Your Jira Cloud site follows this format:
4

Connect in ewake

In your ewake dashboard, go to Integrations → Jira → click Connect with API key.Click Test connection, then Save. ewake detects that your token opens Rovo MCP and records it — the modal confirms the capabilities it verified (issues, and, when your account has access, Confluence and semantic search).
Jira is connected over Rovo MCP. Ewake can now reference your issues, Confluence pages, and search both during investigations.
A Rovo-scoped token is rejected by the Jira REST API by design — that is expected, and it is how ewake tells the two transports apart. If the connection fails, the modal relays Atlassian’s own message, which names the missing scope or the org-admin step.

​
What ewake can do

Once connected, ewake reads from Jira on demand during an investigation:
  • Search issues with a JQL query, returning a compact list (key, summary, status, assignee, type, last updated).
  • Read an issue, returning its full description (as plain text) and comments, to bring the context of the relevant ticket into the investigation.
Over Atlassian Rovo MCP, ewake also gets — when your Atlassian account has access to them:
  • Read Confluence pages, so architecture docs and past postmortems join the investigation.
  • Semantic search across Jira and Confluence, finding the right issue or page by meaning rather than exact keywords.
Over Rovo MCP, ewake only ever calls free, read-only operations. It never spends Rovo credits — metered features such as Rovo Chat, Deep Research, and the Teamwork Graph are blocked at the source.
Ewake uses read-only access to Jira. It never creates, edits, transitions, or comments on issues.

Reach Confluence too →

How ewake reaches Confluence content today through Jira’s Rovo MCP connection.

What does ewake access in Jira? →

The read-only permission model behind every integration.