
Jira and Confluence on your Atlassian Cloud site. Chat with it in its own channel, or @mention it in any channel, and it replies in the thread.
Ask in plain language, with no slash commands. Atlassian (Jira & Confluence) replies in the thread so the whole team sees the result.
These are examples of the kind of request to try. What Atlassian (Jira & Confluence) can do depends on your Atlassian (Jira & Confluence) account and permissions.
Direct channel app. Atlassian (Jira & Confluence) also has a direct connection. Open a channel, choose Apps and Agents from the header menu, then Add app (direct connection), and Atlassian (Jira & Confluence) events land in that channel as they happen.
Read more in the help centre: talk to an installed app, the MCP catalog and installing a channel app.
FabricLoop connects to the Atlassian (Jira & Confluence) MCP server for you, so there is nothing to paste. The endpoint is published here for reference and for debugging.
https://mcp.atlassian.com/v1/mcp/authv2
The Atlassian (Jira & Confluence) MCP server is at https://mcp.atlassian.com/v1/mcp/authv2. FabricLoop connects to it for you when an admin enables Atlassian (Jira & Confluence), so you do not paste the URL anywhere.
An admin enables Atlassian (Jira & Confluence) from the Apps tab under MCP and each person connects their own Atlassian (Jira & Confluence) account. Then select Atlassian (Jira & Confluence) in the left nav or in Messages to chat with it in its own channel, or type @ in any channel, pick Atlassian (Jira & Confluence) and ask in plain language. In a channel it replies in the thread.
Atlassian (Jira & Confluence) replies in the channel thread, so everyone in that channel sees the answer. It uses the connecting person's Atlassian (Jira & Confluence) permissions, and the connection does not expand anyone's membership in FabricLoop.
Often we can add one within a day. Contact us with what you use.
See all integrations · How apps work in FabricLoop · Need one we don't have? Contact us