Scenario 83: Bringing Jira, Notion and Slack information together in a single project view

Who and in what situation

Murat, the digital agency’s client project lead, wants to view the brief in Notion, open issues in Jira and the latest decisions in Slack together before the status meeting.

How it is done today

Murat searches each of the three applications separately, pastes the links he finds into a document and manually compares the information to determine what is up to date.

How to do it with AI

1. Click the + button at the bottom left of the chat, select Connectors > Manage connectors and review the applications in the directory. You can also open the same area through Customize > Connectors > +. [156]
2. Confirm that Notion, Slack, Atlassian MCP, Asana and HubSpot are listed in the directory. The Atlassian MCP description covers other Atlassian applications as well as Jira and Confluence. [157]
3. Authorize your account using the Connect or Install button; review the read and write capabilities on the connector’s page. Enable only read tools initially. [157] [156]
4. Under Connectors in the chat menu, enable only the connectors needed for this conversation. Murat could say, “Compare the latest decisions, open Jira issues and delivery requirements in the brief for the {CLIENT} project.”
5. Even if a write tool is enabled, ask to see the draft and require human approval before any new Jira issue, Slack message or Notion change. Organization owners can restrict tool permissions under Tool permissions. [156]

Example prompt

Read only content from the last {DATE_RANGE} in Notion, Jira and Slack for the {CLIENT} project. Compare decisions, open issues, conflicting dates and missing owners in a table with source links. Do not modify any records or send messages.

Evidence and real-world example

Anthropic’s verified directory includes Notion, Slack, Atlassian MCP, Asana and HubSpot. A published Anthropic-Salesforce example describes how Slack MCP is used to read channels, messages and files to generate a conversation summary, extract decisions and draft an update. [157] [158]

Points to consider

A remote MCP connector is called from Claude’s cloud infrastructure; a server on an internal company VPN may not work unless the necessary network access is granted. Read the OAuth scopes requested during connection, do not add servers you do not trust and consider the risk of prompt injection from content containing hidden instructions. [146] [156]

Sources for this scenario

146. Get started with custom connectors using remote MCP (support.claude.com)
156. Use connectors to extend Claude's capabilities (support.claude.com)
157. Connectors and plugins (claude.com)
158. Salesforce and Anthropic expand partnership (anthropic.com)