Discover Slack modules
Inspect the Slack connector’s available actions, required fields and authorized connections before selecting a message operation.
Your connection path
SlackCursor
Stacksync MCP OAuth
Your assistant works through your Stacksync workspace and its available connections.
First request
“Design a sync-issue alert”
Stacksync MCP · Communications
Connect Slack to Cursor with MCP.
Use Stacksync MCP to inspect Slack actions and prepare notifications inside broader business workflows. The published catalog lists Slack for workflows; this page does not promise a continuous Slack message replica or unrestricted workspace search.
01 / The connection
How Slack works with Cursor
Use Stacksync MCP to inspect Slack actions and prepare notifications inside broader business workflows. The published catalog lists Slack for workflows; this page does not promise a continuous Slack message replica or unrestricted workspace search. Add the Stacksync MCP server to Cursor, then use the connection path below.
The server belongs to Stacksync. The available Slack operations depend on your connection, permissions, and connector modules.
Explore the Slack connector →02 / Capabilities
Slack capabilities through MCP
Choose the connection path that fits the job. Your assistant inspects the available tools before configuring or running an action.
Prepare business notifications
Build a proposed alert from a known workflow or sync event, with a chosen channel and an exact message payload.
Review Slack workflow failures
Inspect the steps and outputs of an existing workflow to identify a failed Slack action and prepare a targeted correction.
03 / Setup
Set up Stacksync MCP in Cursor
Connect the MCP server first. Then connect Slack using the requirements below.
Code editorCursor
Use Stacksync from Cursor by adding a remote server to its MCP configuration.
Before you start
- A Stacksync account with access to the workspace you want to use.
- Permission to add an external MCP server in your AI client.
- Cursor installed with permission to configure MCP servers.
Add the server configuration
Merge this stacksync entry into the mcpServers object in ~/.cursor/mcp.json. Preserve any servers you already use.
{ "mcpServers": { "stacksync": { "url": "https://mcp.stacksync.com/mcp" } } }Connect from Cursor
Open Cursor’s MCP settings, select Connect beside stacksync and finish the Stacksync sign-in in your browser.
Check your workspace
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Check the connection
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Slack connection and capabilities.
04 / Put it to work
Slack workflow prompts
Example prompts for Slack in Cursor. The outcomes describe what to expect, not results from your account. Review the proposed configuration before running it.
01
Connector actions
Design a sync-issue alert
Inspect my Stacksync syncs, Slack modules and existing alert workflows. Propose an alert for the sync I choose, using a verified Slack action and the channel I specify. Include the sync name, failure summary and a link where available, with duplicate-alert handling. Show the message and trigger configuration before saving or sending anything.
What to expect
A proposed operational alert scoped to one sync and one Slack channel.
02
Connector actions
Prepare a deal-win notification
Inspect the available CRM and Slack modules and connections. Propose a workflow that formats an approved closed-won deal event for the channel I choose. Verify the event source and message action, list the permitted deal fields and show a sample using placeholders. Do not send a message, activate a trigger or deploy the workflow yet.
What to expect
A channel-specific notification proposal with a verified event source and minimal deal fields.
03
Connector actions
Investigate a failed Slack step
Find the workflow I name and inspect the failed run and Slack step output. Identify whether the failure concerns channel access, action inputs or the upstream payload. Propose a correction and explain whether replaying the whole run could duplicate earlier messages. Do not replay or send anything until I choose the recovery action.
What to expect
A targeted recovery proposal that accounts for already-completed workflow steps.
05 / Before you run
Requirements and limitations
What you need
- Connect your AI client to Stacksync MCP, sign in and select the workspace before inspecting its resources.
- Reuse an authorized app connection or open the secure connection link from Stacksync. Enter credentials in the connection form, never in the chat.
- Confirm the target Slack workspace and channel, and verify that the connected account can perform the chosen action there.
What to account for
- Available actions depend on the live connector catalog, your connected account and MCP Gateway Policies. Inspect the action and its form before using it.
- The public app catalog lists Slack as a workflow connector, not a sync connector. It does not establish arbitrary message history or search access.
- Posting a message changes an external system. Review the channel, recipients and content before running a proposed action.
Your workspace. Your permissions.
OAuth access follows your Stacksync role. Choose read-only access during sign-in when appropriate. Workspace owners can enable “Ask before every change”; it is a configurable setting. Direct connector actions also follow gateway policies.
Read about permissions and approvals ↗If setup does not work
- The MCP server does not appear
- Check your client’s custom MCP settings and any plan or administrator prerequisites. Reconnect using the setup instructions above.
- Your workspace or app is missing
- Verify the Stacksync account and workspace selected during OAuth, then inspect the workspace’s connections. Add missing app credentials through the secure connection flow.
- An action is unavailable or denied
- Inspect the current connector modules and required inputs. Check your workspace role, read-only consent, gateway policy, and the source app’s API permissions.
06 / Common questions
Slack MCP questions
Is this a Slack message sync?
No continuous Slack sync is established by the published app catalog. The supported path described here is discovering connector actions and using them in Stacksync workflows.
Can an assistant search all Slack messages through this connection?
Do not assume that. Inspect the current Slack modules and the connection’s permissions. The public catalog confirms workflow availability, not a universal message-search action.
Can Slack notifications require review?
The sample prompts ask for a proposal before sending. Workspace owners can also enable Ask before every change for MCP operations. Review the target channel as well as the message.
Reviewed · Product documentation and connector references
Keep building
