The Slack MCP connector lets Spark read from and write to Slack directly inside your conversations. Instead of copy-pasting messages into Spark, you can ask Spark to search channels, pull thread context, and post updates back to your team, all without leaving your workflow.
This article covers what an admin needs to do before anyone can connect, and how each user connects from the Spark Connectors list.
In this article:
- Step 1: Installing the Productboard Slack app
- Step 2: Connecting Slack in Spark
- What Spark can do with Slack
- Example prompts
- Current limitations
- See also
Step 1: Installing the Productboard Slack app
Note: If the Productboard Slack app is already installed in your workspace (for example, if your team already pushes Slack messages to Productboard as feedback), you can skip this step. The same app powers both the feedback integration and the Spark MCP connector.
You must be a Slack admin to install apps in your workspace. If you are:
- Open the Productboard app in the Slack App Directory.
- Click Add to Slack.
- Review the requested permissions and click Allow.
The app is now installed for your Slack workspace. Users can proceed to connect Slack from within Spark.
Step 2: Connecting Slack in Spark
Each user connects Slack from their own Spark session. The connection is personal and persistent across all your Spark chats once established.
- From any Spark chat, click Integrations and connectors > Add integrations and connectors.
- Find Slack in the list and click its name to review details, then click Connect.
- You'll be redirected to Slack. Review the permissions Spark is requesting and authorize the connection.
- Slack is now active and available in all your Spark chats.
Tip: Specify which tool you want Spark to use by naming it in your prompt: "Search Slack for messages about the checkout redesign in #product-feedback."
What Spark can do with Slack
Once connected, Spark can:
- Search channels: Find messages across public and private channels you have access to.
- Read messages and threads: Pull the full context from a thread, including replies.
- Access direct messages: Read DMs where you're a participant.
- Post messages: Send updates or summaries to any channel or DM you can write to.
Spark can only access the channels, threads, and DMs that your Slack account has permission to see. It cannot access private channels you're not a member of.
Example prompts
Once Slack is connected, try prompts like these:
- "Search Slack for messages mentioning checkout errors in #support this week."
- "What did the team discuss in the #product-feedback channel about the onboarding flow?"
- "Pull the latest thread from #pm-team about the Q3 roadmap and summarize it."
- "Post a summary of today's opportunity findings to #product-weekly."
Current limitations
- Spark can access channels and DMs that your personal Slack account has permission to see. It cannot access private channels you're not a member of, even if a teammate has connected their Slack account.
- The Slack connection is per-user. If a teammate wants Spark to access Slack on their behalf, they need to connect their own account using the instructions in step 2 above.
- MCP connectors with write permissions (such as posting messages) may execute without a confirmation prompt. Review your prompt carefully before asking Spark to post on your behalf.