How to connect Jira and Confluence to Grok

Short answer

Grok has no Jira or Confluence connector. Connect Atlassian to Upsy once, which covers both Jira and Confluence on one Cloud site, then add Upsy to Grok as a custom connector. It takes about five minutes. You need an Atlassian Cloud site, and your Atlassian admin may have to allow the connection first.

The built-in way

Grok's connector docs list its built-in connectors (Gmail and Google Calendar, Google Drive, OneDrive, Outlook, Teams, SharePoint and Salesforce) and a catalog that includes Linear, Notion and GitHub. Jira and Confluence aren't in either.

Atlassian has its own server, the Atlassian Rovo MCP server. An MCP server is a connector that lets an assistant use another app. It left beta in February 2026, and Atlassian's admins control which AI tools may sign in to it. Neither Grok nor Upsy is on Atlassian's default list of allowed domains, so an organization that enforces it needs an admin to allow the tool once.

What you get by going through Upsy:

• Read-only access per assistant, so Grok can report on a sprint without touching it.
• Pick actions: for example, comment and move issues between statuses, but never create pages.
• More than one site. Each Atlassian sign-in covers one site. Upsy holds up to five Atlassian connections.
• Other apps in the same chat. Turn a Slack thread, an email or meeting notes into a Jira issue.
• A History of every issue and page Grok touched.

What you need

• An Atlassian Cloud site with Jira, Confluence or both. Atlassian says all Cloud customers have access. Its docs don't mention Data Center or Server.
• Your own access to the projects and spaces you want. The server only sees what you can see.
• An Atlassian admin's go-ahead, if your organization limits AI tools by domain, network or permission. Admins manage this in Atlassian Administration under Rovo › Rovo MCP server.
• Grok on grok.com. On Grok Business or Enterprise, a team admin adds connectors first.
• A free Upsy account.

Atlassian limits calls per site, per hour:

Connect Jira and Confluence to Grok

1. Sign up at upsy.ai with Set up Upsy.
2. On Upsy's Apps page, find Atlassian (it says "Jira and Confluence") and click Connect.
3. Atlassian's consent screen opens. Pick the site you want Grok to use and approve. If you have more than one site, you can connect Atlassian again later for the next one.
4. On the Assistants page, click Add assistant, then pick Grok under Which assistant? Upsy shows a setup prompt and its address, https://upsy.ai/connect.
5. In Grok, either:
   • paste the setup prompt into a chat, approve the card Grok shows, and open the sign-in link, or
   • open Connectors on grok.com, click New Connector, then Custom, paste the address and sign in. The custom connector guide shows each step.
6. On the Upsy page that opens, sign in and choose Atlassian's level for Grok, then click Allow.
7. Paste the Help Grok remember message into Grok, so it uses Jira and Confluence in later chats without being told.

Already using Upsy with Grok? Steps 2 and 3 are all you need. Atlassian starts at Full access for every assistant, so set a narrower level on its page in Upsy if you want one.

For Grok Bot, paste the setup prompt into a Bot chat, then type @ and pick Upsy when you start a task.

Check that it works

Ask Grok: "Using Upsy, which Atlassian site am I connected to? List my open Jira issues, highest priority first."

Grok should name your site, then list your issues with their keys, such as PROJ-142, and statuses. Then try Confluence: "Find our onboarding page in Confluence and summarize it in five bullets."

What Grok can do with Jira and Confluence

The server works within your own Atlassian permissions. In plain words:

Jira

• Search issues with JQL, Jira's query language. Grok writes the query for you.
• Read an issue with its comments, links and available transitions.
• Create issues, edit fields, move an issue to another status, and add comments.
• Look up projects, issue types and people, for example to assign someone.

Confluence

• Search pages with CQL, Confluence's query language.
• Read pages, their child pages and comments.
• Create and update pages, and add footer or inline comments.

Across both: Rovo search, Atlassian's search across your Jira, Confluence and connected tools.

There's no tool to delete Confluence pages, and Jira deletes stay off unless an Atlassian admin turns them on. Atlassian is moving the server to a new version with more tools, such as boards, sprints and worklogs. Existing connections switch over automatically on March 1, 2027.

Set a level for Atlassian, per assistant:

• Read-only: search and read only, for stand-ups, sprint reports and finding docs.
• Pick actions: only the tools you tick. For example, comment and transition issues but not create pages. Any tool Atlassian adds stays off until you tick it, which matters with the new version coming.
• Full access: every tool your Atlassian admin allows.
• No access: Grok can't reach Jira or Confluence.

Prompts to try

• "What's still open in the current sprint of the WEB project? Group it by assignee and flag anything not updated in five days."
• "Read the #incidents Slack thread from this morning and create a Jira bug in OPS with the steps to reproduce. Show me the draft first."
• "Write my stand-up: what I moved to Done yesterday in Jira, and what's In Progress now."
• "Find the on-call runbook in Confluence and tell me who to page for a database outage."
• "Create a Confluence page under Release Notes for version 2.4, listing every Jira issue fixed in that version."
• "Which Jira issues mention Acme in a comment from the last month?"

The Slack prompt needs Slack connected too. See connect Slack to Grok.

Troubleshooting

"Your organization admin has not authorized the write permission"

Atlassian admins can turn Read, Write and Search on or off for each app. This message means Write is off for your organization. Ask an admin to change it under Rovo › Rovo MCP server › Permissions. Changes apply right away.

The Atlassian sign-in is refused

Your organization may only allow AI tools on its domain list. An admin can add a domain under Atlassian Administration › Rovo › Rovo MCP server. Atlassian allows its own list of partners by default, and Upsy isn't on it.

"You don't have permission to connect from this IP address"

Your site uses IP allowlisting. Requests come from Upsy's servers, not your laptop, so being on the company VPN doesn't help. An admin has to allow them.

Grok sees the wrong site, or only one of your sites

Each sign-in connects one site. Connect Atlassian again on Upsy's Apps page and choose the other site. Both then show up for Grok, each with its own level.

Results come back empty or partial

Atlassian says this usually means an expired session or a missing permission. Reconnect Atlassian on Upsy's Apps page and approve everything it asks for. More fixes are in Grok connectors not working.

Requests start failing during a big report

You've hit the site's hourly limit, which on Free is 500 calls. Narrow the request to one project or one sprint, or wait for the next hour.

Security and privacy

• Grok never gets your Atlassian login. Upsy holds the sign-in and calls Atlassian's server for Grok.
• Atlassian's rules come first. Your own permissions, your admin's Read, Write and Search settings, domain rules and IP allowlists all still apply. Atlassian says its server doesn't store or cache your Jira or Confluence content.
• History in Upsy lists every Jira and Confluence call Grok made, under Grok's name.
• Alerts: Upsy emails you if one assistant deletes 50+ items or reads 100+ items within 10 minutes. You also hear when a new assistant or app connects.
• Turning it off: set Atlassian to No access for Grok, turn Grok off with one click, or disconnect Atlassian in Upsy.

FAQ

Can Grok create Jira tickets?

Yes, once Atlassian is connected through Upsy with Full access, or with Pick actions and the create tool ticked. Grok can also edit fields, change status and comment.

Is there a Grok Jira integration built in?

No. Grok's docs list no Jira or Confluence connector. Upsy connects to Atlassian's own MCP server, and you add Upsy to Grok as a custom connector.

Can Grok read Confluence pages?

Yes. One Atlassian connection covers Confluence too. Grok can search, read, create and update pages and comments that you have access to.

Does it work with Jira Data Center?

Atlassian's MCP server is for Atlassian Cloud sites. Its docs don't cover Data Center or Server.

Can Grok delete Jira issues?

Not by default. Atlassian keeps Jira deletes off unless an admin enables them, and there's no Confluence delete tool. Upsy's Read-only and Pick actions can rule them out for Grok as well.