A
securityA
licenseA
qualityRun your own runbooks from Claude Desktop.
You can create your runbooks and execute them with other MCP servers.
Last updated -
2
1
Python
Apache 2.0
Slack is a collaboration hub that connects your organization's people, information, and tools. It's a platform for team communication where work flows seamlessly between direct messaging, group conversations, and dedicated channels for projects, topics, or teams.
Why this server?
Allows sending notifications and alerts to Slack channels, particularly for sharing operational information such as Kubernetes pod status
Why this server?
Provides access to Hackle's A/B testing data through the Hackle Slack Community, where users can request API keys for the MCP Server
Why this server?
Allows ingestion of content from Slack channels into Graphlit for search and retrieval
Why this server?
References community access through Slack for support and collaboration with other users.
Why this server?
Connects with Slack to enable community engagement and collaboration through a dedicated channel.
Why this server?
Allows Claude to interact with Slack workspaces, including listing channels, posting messages, replying to threads, adding reactions, getting channel history, getting thread replies, and retrieving user information.
Why this server?
Enables community engagement through the #steampipe Slack channel for support and collaboration
Why this server?
Provides community support through the linked Slack community
Why this server?
Monitors Slack's operational status and provides real-time information about service availability and component health.
Why this server?
Enables sending messages to Slack channels, as shown in the example 'Send a message in slack to the #general channel with today's weather'
Why this server?
Allows interaction with Slack Workspaces, providing tools to retrieve channel histories and list available channels without requiring admin permissions or bot approvals.
Why this server?
Provides tools for interacting with Slack API, including listing channels, posting messages, replying to threads, adding reactions, retrieving channel history, getting thread replies, retrieving user information, and searching messages in a Slack workspace.
Why this server?
Enables configuration and control of Slack integration with GitLab projects.
Why this server?
Allows Claude to interact with Slack workspaces as a user, including listing channels, posting messages, replying to threads, adding reactions, getting channel history, getting thread replies, retrieving user lists, and viewing user profiles
Why this server?
Supports retrieval and management of Slack messages through the Unipile messaging platform.
Why this server?
Allows sending notification messages to Slack channels via a Slack Connector, supporting features like alerting on availability problems and security vulnerabilities.
Why this server?
Enables interaction with Slack through Fastn's connector system
Why this server?
Enables posting Devin AI tasks to Slack channels, maintains thread context between Devin sessions and Slack threads, and allows sending messages to both Devin sessions and corresponding Slack threads simultaneously.
Why this server?
Enables interaction with Slack workspaces using a bot token, allowing communication and operations within specified teams
Why this server?
Provides tools for connecting to Slack workspaces and making API requests, enabling interaction with Slack channels, messages, users, and other Slack resources.
Why this server?
Mentioned only as a community link, not as an integration target of the MCP server.
Why this server?
Framework ready for implementation, planned to support Slack integration with a similar feature set to Google Chat.
Why this server?
Enables AI assistants to interact with Slack workspaces, providing tools for reading and sending messages, managing channels, handling user information, uploading and sharing files, searching across workspace content, and adding emoji reactions.
Why this server?
Enables querying of Slack data by exposing it as relational SQL models through the CData JDBC Driver.
Why this server?
Provides SQL query capabilities for Slack messaging platform data.
Why this server?
Provides SQL access to Slack channels, messages, and workspace data
Why this server?
Provides access to Slack messaging platform data including channels, messages, and users.
Why this server?
Listed as a supported data source for integration with the MCP server, allowing access to Slack data.
Why this server?
Enables read-only access to Slack messages, channels, and users.
Why this server?
Enables querying Slack messaging data through SQL.
Why this server?
Listed as a supported data source for accessing Slack messaging and workspace data.
Why this server?
Allows querying Slack channels, messages, and users using SQL.
Why this server?
Provides SQL-based access to Slack messaging and workspace data.
Why this server?
Enables querying and retrieving message and channel data from Slack workspaces.
Why this server?
Enables querying Slack messaging platform data through SQL models.
Why this server?
Listed as a supported data source for integration through the CData JDBC driver.
Why this server?
Enables reading Slack messaging data through SQL interfaces, allowing natural language querying of team communication information.
Why this server?
Listed as a supported data source in the compatibility table, enabling access to Slack data.
Why this server?
Offers Slack integration with a community workspace for collaboration and support
Why this server?
Enables read-only access to Slack messaging data, allowing queries for channels, messages, users, and workspace information.
Why this server?
Provides SQL access to Slack channels, messages, and workspace data.
Why this server?
Listed as a supported data source for integration, allowing access to Slack data through the MCP server.
Why this server?
Enables querying of Slack workspace, channel and message data through relational SQL models.
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver
Why this server?
Provides read-only access to Slack data through a relational SQL interface, allowing queries for information about channels, messages, users, and other Slack resources.
Why this server?
Provides access to Slack messaging data including channels, messages, users, and other collaboration information through SQL queries.
Why this server?
Enables interaction with Slack's API to perform operations like posting messages, retrieving user information, and listing conversations
Why this server?
Provides access to Slack discussions as a resource type, enabling search and retrieval of conversation content from Slack channels
Why this server?
Enables AI assistants to interact with Slack workspaces by listing channels, sending messages, replying to threads, adding reactions, retrieving channel history, getting thread replies, and accessing user information.
Why this server?
Mentioned as a planned future integration for sending notifications about encoding job status and issues
Why this server?
Provides a community support channel for users of the MCP server.
Why this server?
Enables automated alerts to be sent to Slack channels via webhooks when price drops are detected, with customizable message formatting
Why this server?
Provides authenticated interactions with Slack including reading channels, writing messages, and adding reactions with configurable permission scopes.
Why this server?
Planned integration for interacting with Slack workspaces, likely enabling message sending and workspace management through the MCP server
Why this server?
Mentioned as a planned future integration in the roadmap, but not currently implemented.
Why this server?
Provides access to Slack actions through ActionKit, allowing Claude to interact with and perform operations in Slack workspaces on behalf of authenticated users.
Why this server?
Provides the ability to interact with a Slack workspace by posting messages to channels and retrieving a list of all workspace users
Why this server?
Provides tools for accessing Slack's search functionality, allowing users to retrieve workspace information (users, channels), fetch messages from specific channels, get thread replies, and search through messages across the workspace.
Why this server?
Provides integration with Slack, allowing the MCP server to interact with Slack's API