How to connect Jira and Confluence to Meta Muse

Muse has no Jira connector of its own. Connect Jira and Confluence to Muse so it can find and update issues and read your team's pages.

Updated

Short answer

Muse doesn't have a Jira or Confluence connector. To add them, connect Atlassian in Upsy, then paste one prompt into Muse. Muse then reaches Atlassian's own MCP server (a connector Atlassian runs so assistants can use Jira and Confluence) through Upsy. It takes about five minutes, works on Muse's free plan, and needs an Atlassian Cloud site. Your Atlassian admin may have to allow Upsy first.

The built-in way

There isn't one yet. Meta's connector list, in its September 29 announcement, includes Asana, Notion and Slack for work, but nothing from Atlassian. Check Settings › Connectors in Muse in case that changes.

Muse can build a custom connector for a service it doesn't support, if you ask it in chat. Meta's connectors help page warns that Meta doesn't review custom connectors or how they use your data. Going through Upsy doesn't change that Muse is using a custom connector, but you get three things on top:

  • You choose which Jira and Confluence actions Muse can take, not just on or off.
  • Every action is in Upsy's History, under Muse.
  • Grok, ChatGPT and Claude can use the same Atlassian connection, each with its own access.

What you need

  • An Atlassian Cloud site with Jira, Confluence or both. Atlassian's MCP server only works with Cloud, not Jira Data Center or Server (Atlassian's MCP server docs).
  • Rovo credits. Atlassian charges each MCP call against your organization's Rovo credits, the same pool Rovo Chat and Rovo agents use (Atlassian support).
  • Possibly your admin. An Atlassian org admin controls which outside tools can connect, from Atlassian Administration › Rovo › Rovo MCP server. If your company limits this, they'll need to allow Upsy (see Troubleshooting).
  • A Muse account. Muse is for adults in the US and Canada.
  • A free Upsy account.

Connect Jira and Confluence to Muse

  1. Go to upsy.ai and click Set up Upsy.
  2. On Upsy's Apps page, find Atlassian (it covers both Jira and Confluence) and click Connect. Atlassian's consent page opens. Sign in with your Atlassian account and approve access.
  3. On Upsy's Assistants page, click Add assistant, then choose Muse under Which assistant?.
  4. Copy the prompt under Paste this into Muse and paste it into a Muse chat, in the app or at muse.ai.
  5. Muse adds a custom connector named Upsy and shows a link or button to sign in. Open it, sign in to Upsy, and choose what Muse can use. Leave Atlassian ticked. Choose Read-only if Muse should only look things up.
  6. Copy the Help Muse remember message Upsy shows and paste it into Muse, so it uses Upsy for Jira in later chats without being told.

You only connect Atlassian once. Muse doesn't see your Atlassian sign-in: it asks Upsy, and Upsy calls Atlassian.

Check that it works

Send Muse: "Use Upsy to list the Jira issues assigned to me that aren't done, with their status."

Muse should find your site, run a Jira search (in JQL, Jira's query language, something like assignee = currentUser() AND statusCategory != Done) and list the issues with their keys. The search shows up in Upsy's History under Muse.

What Muse can do with Jira and Confluence

The tools are Atlassian's own (supported tools), and they only show Muse what your Atlassian account can already see. In plain words:

Jira

  • Search issues with JQL, and read an issue with its comments, history and worklogs.
  • Create and edit issues, change their status, and assign them.
  • Add comments, log work, and link issues to each other.
  • Look up projects, boards, sprints and people.

Confluence

  • Search pages and read pages, blog posts, comments and spaces.
  • Create pages and update them.
  • Add comments.

Across both

  • Atlassian's search finds things in Jira and Confluence at once.

Deleting issues and managing projects are off on Atlassian's side until an Atlassian admin turns them on. Atlassian is also moving to a larger tool set (its "v2" server), so tool names can change over time. Ask Muse to list them whenever you like.

In Upsy, Muse gets one of four levels for Atlassian:

Level What it means here
Full access Every tool Atlassian gives
Read-only Only tools Atlassian marks as read-only, like searching and reading issues and pages. A tool Atlassian hasn't marked counts as one that can change things
Pick actions Only what you tick, for example "add comment" and "edit issue" but not "create issue"
No access Muse doesn't see Atlassian

Change it on Muse's page in Upsy (Assistants › Muse).

Prompts to try

  • "What's left in the current sprint on the WEB board? Sort it by priority."
  • "Create a bug in project WEB: the checkout button is cut off on iPhone. Priority High, assign it to me."
  • "Move WEB-142 to In Review and comment that the fix is on staging."
  • "Find our on-call page in Confluence and tell me who's on call this week."
  • "Write a Confluence page in my personal space that summarizes the issues I closed this week."
  • "Read the email from Dana about the login bug and turn each problem she lists into a Jira issue." (This needs Gmail connected in Upsy too.)

Troubleshooting

"Your organization admin must authorize access from this redirect URL"

Your Atlassian organization only lets approved tools connect. An org admin has to add Upsy's address (for example https://upsy.ai/**) in Atlassian Administration › Rovo › Rovo MCP server, under the domain settings. Atlassian's fix for this error suggests trying again in a private window afterwards. Note that the address to allow is Upsy's, not Muse's: Upsy is what talks to Atlassian.

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

Your organization uses an IP allowlist. Requests come from Upsy's servers, not from your phone or laptop, so a VPN won't help. Ask your admin.

Sign-in worked, but Muse gets "403" errors

Atlassian accepted the sign-in but refused the action. Usually your own account lacks permission in that project or space, or a policy blocks it. Check that you can do the same thing yourself in Jira.

Muse can't delete an issue

That's Atlassian's default: delete tools are off until an Atlassian admin turns them on. You can still ask Muse to close or move an issue.

Jira Service Management tools are missing

Atlassian only offers those tools with an API token, and Upsy connects with Atlassian's sign-in instead. Jira Software and Confluence work as normal.

Muse acts on the wrong site

If your account has several Atlassian sites, name the one you mean: "Use acme.atlassian.net."

Muse opens Jira in a browser instead

Muse has its own browser and may try it. Say "use Upsy's Jira tools", or paste the Help Muse remember message again.

Security and privacy

  • Atlassian's rules still apply. Muse only sees what your account can see, project and space permissions included. Atlassian also records each MCP action in its audit log, and admins can review or revoke access.
  • Upsy's record. Every call Muse makes is in Upsy's History, under Muse.
  • Defaults. A newly connected app starts at Full access for every assistant you've added. Set Atlassian to Read-only or Pick actions on Muse's page if that's too much.
  • Emails. Upsy emails you when a new assistant connects to your Upsy or a new app is connected.
  • Turning it off. One click on Muse's page cuts it off. Disconnect Atlassian on Upsy's Apps page to remove it for every assistant. You can also revoke Upsy from your Atlassian account settings.
  • No extra prompts. Upsy doesn't ask you before each action. Muse's own approval settings decide when it checks with you.

Upsy is free for personal use, has no ads and doesn't sell your data.

FAQ

Does Meta Muse integrate with Jira?

Not natively. Meta's connector list has no Jira or Confluence. You can add them as a custom connector through Upsy, which uses Atlassian's own MCP server.

Can Muse create Jira issues?

Yes, with Full access or with "create issue" ticked under Pick actions. It can also edit them, comment and change their status.

Does it work with Confluence?

Yes. The same Atlassian connection covers Confluence: Muse can search and read pages, and create or update them if you allow it.

Does it work with Jira Data Center or Server?

No. Atlassian's MCP server only connects to Atlassian Cloud sites.

Does using Jira through Muse cost anything?

Muse's free plan and Upsy are free, but Atlassian counts each MCP call against your organization's Rovo credits.

Can Grok use the same connection?

Yes. Add Grok to Upsy and it uses the same Atlassian connection, with its own access. See how to connect Jira and Confluence to Grok, or compare the two agents in Grok Bot vs Muse.

Related guides