Discover Slack modules
Inspect the Slack connector’s available actions, required fields and authorized connections before selecting a message operation.
Your connection path
Your assistant works through your Stacksync workspace and its available connections.
“Design a sync-issue alert”
Stacksync MCP · Communications
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
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. Choose an AI client below to get started with the Stacksync MCP server.
The server belongs to Stacksync. The available Slack operations depend on your connection, permissions, and connector modules.
Explore the Slack connector →02 / Capabilities
Choose the connection path that fits the job. Your assistant inspects the available tools before configuring or running an action.
Inspect the Slack connector’s available actions, required fields and authorized connections before selecting a message operation.
Build a proposed alert from a known workflow or sync event, with a chosen channel and an exact message payload.
Inspect the steps and outputs of an existing workflow to identify a failed Slack action and prepare a targeted correction.
03 / Setup
Connect the MCP server first. Then connect Slack using the requirements below.
Connect Claude on the web or desktop to Stacksync through a custom connector and browser sign-in.
Open Customize → Connectors, select + Add, then Add custom connector. Name it Stacksync and use the server URL below.
https://mcp.stacksync.com/mcp Select Connect, complete the Stacksync sign-in in your browser and choose the default workspace. Clear Make changes on the consent screen if you only want read access.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Slack connection and capabilities.
Add the remote Stacksync server to Claude Code and authenticate from its MCP menu.
Run the command below. Add --scope user if you want the connection available across your projects.
claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp Open Claude Code, run /mcp, select stacksync and complete the Stacksync sign-in. Choose the workspace you want requests to use by default.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Slack connection and capabilities.
Add Stacksync as a custom MCP app in ChatGPT and sign in with OAuth.
Open Settings → Apps → Advanced settings and turn on Developer mode. If the option is unavailable, check the account or workspace policy with your administrator.
Select Create app, name it Stacksync, enter the server URL below and choose OAuth. Complete the Stacksync sign-in and select your default workspace.
https://mcp.stacksync.com/mcp Select Stacksync from the chat tools menu so the conversation can use its tools. Signing in to ChatGPT itself does not sign you in to Stacksync.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Slack connection and capabilities.
Configure Stacksync in Codex with a remote MCP URL and an explicit OAuth login.
Add the Stacksync endpoint to your Codex MCP configuration.
codex mcp add stacksync --url https://mcp.stacksync.com/mcp Run the login command and complete the Stacksync browser sign-in. Select a default workspace; restart your Codex session if the tools are not yet listed.
codex mcp login stacksync Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Slack connection and capabilities.
Use Stacksync from Cursor by adding a remote server to its MCP 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"
}
}
} Open Cursor’s MCP settings, select Connect beside stacksync and finish the Stacksync sign-in in your browser.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Slack connection and capabilities.
Connect Stacksync to GitHub Copilot Chat in VS Code using an HTTP MCP server.
Run the command below. Alternatively, add a stacksync entry with type http and this URL under servers in your project’s .vscode/mcp.json.
code --add-mcp '{"name":"stacksync","type":"http","url":"https://mcp.stacksync.com/mcp"}' Open Copilot Chat in Agent mode. Start stacksync from the tools picker and complete the Stacksync browser sign-in.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Slack connection and capabilities.
Add Stacksync to Cascade with Windsurf’s serverUrl configuration and OAuth sign-in.
In the Cascade panel, open the … menu and select Open MCP config file. Merge this entry into mcp_config.json without removing other servers.
{
"mcpServers": {
"stacksync": {
"serverUrl": "https://mcp.stacksync.com/mcp"
}
}
} Save the configuration. Cascade opens the Stacksync sign-in flow the first time it uses the server. Choose your default 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.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Slack connection and capabilities.
Connect the Gemini command-line client to Stacksync through remote HTTP MCP and browser authorization.
Run the following command in your terminal to add the HTTP server.
gemini mcp add --transport http stacksync https://mcp.stacksync.com/mcp Start Gemini CLI, run the command below and finish the Stacksync sign-in in your browser.
/mcp auth stacksync Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
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
Example prompts for Slack. The outcomes describe what to expect, not results from your account. Review the proposed configuration before running it.
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.
A proposed operational alert scoped to one sync and one Slack channel.
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.
A channel-specific notification proposal with a verified event source and minimal deal fields.
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.
A targeted recovery proposal that accounts for already-completed workflow steps.
05 / Before you run
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 ↗06 / Common questions
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.
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.
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