💬 Slack MCP Server

🚀 Give your AI assistants direct access to Slack. List channels, read message history, post updates, manage memberships, and surface workspace insights via the Model Context Protocol. No human handoffs needed.

🕒 Last updated: 2026-04-16 · 📋 6 tool categories · 🔐 Scoped bot tokens · 💬 Read + write access · 🤖 MCP-compatible

The Slack MCP Server bridges MCP-enabled AI copilots with the Slack Web API. It lets agents browse channels, retrieve message history, post replies, manage memberships, and pull workspace metadata, all through a standard MCP interface.

Whether you are an operations leader automating status reporting, a support manager enabling AI-driven ticket triage, or an AI platform owner building copilot experiences, this tool provides secure, auditable Slack access for your AI workflows.

🎯 Target Audience	💡 Primary Use Cases
Operations leaders, support managers, AI automation specialists, platform engineers	AI-driven ticket triage, automated status updates, stakeholder alerts, knowledge-base enrichment, channel management

---

📋 What the Slack MCP Server does

• 📋 List channels. Browse public and private channels with pagination support.
• 🕰️ Read history. Retrieve recent message history for context-aware AI assistance.
• 💬 Post messages. Send channel replies, threaded updates, or direct messages.
• 🧑 Manage members. Handle channel memberships and invitations.
• 🛠️ Channel ops. Create, archive, and document channels with topics or descriptions.
• 📊 Pull metadata. Fetch team, channel, and user metadata for reporting.

Each MCP response returns structured JSON that your AI assistant can parse and act on immediately.

💡 Why it matters: letting AI agents interact with Slack directly eliminates copy-paste workflows, reduces manual triage, and keeps stakeholders informed in real time.

---

🎬 Full Demo

🚧 Coming soon: a 3-minute walkthrough.

---

⚙️ Input

Input	Type	Default	Behavior
slackBotToken	string	-	Bot token with required Slack scopes (e.g., xoxb-...).
defaultChannelId	string	-	Fallback channel for writes when the tool call omits one.
method	string	-	MCP method: initialize, tools/list, tools/call, resources/list, resources/read.
params	object	-	Payload for the chosen MCP method.

Example: initialize the MCP connection.

{
    "method": "initialize",
    "slackBotToken": "xoxb-your-token",
    "defaultChannelId": "C012ABCDEF"
}

Example: list available tools.

{
    "method": "tools/list",
    "slackBotToken": "xoxb-your-token"
}

⚠️ Good to Know: This Actor runs in standby mode. Deploy it once, then POST MCP requests to /mcp?token=YOUR_APIFY_TOKEN. The bot token is passed per-request and is never stored.

---

📊 Output

🧾 Schema

Field	Type	Example
🛠️ tools	array	List of available Slack automation tools
📋 name	string	"list_channels"
📝 description	string	"List channels in the Slack workspace"
📦 inputSchema	object	JSON schema for tool arguments

📦 Sample records

---

✨ Why choose this Actor

	Capability
📋	Full channel access. List, read, post, and manage channels and messages.
🔐	Scoped tokens. Per-request authentication with no stored credentials.
🤖	MCP standard. Works with Cursor, Claude, and any MCP-compatible agent.
💬	Read and write. Both message retrieval and posting in one tool.
📊	Metadata access. Team, channel, and user info for reporting.
⚡	Standby mode. Always-on endpoint for instant responses.
💰	Pay per event. Billed only when tool or resource calls succeed.

📊 6 tool categories covering channels, messages, memberships, metadata, creation, and archival.

---

📈 How it compares to alternatives

Approach	Cost	Capabilities	Auth	Setup
⭐ Slack MCP Server (this Actor)	$5 free credit	Full read + write via MCP	Scoped bot token	⚡ 15 min
Custom Slack bot	Server costs	Full control	OAuth app	🕒 Hours
Manual Slack usage	Free	Limited to UI	User login	🕒 Ongoing
Generic webhook	Varies	Write-only	Webhook URL	🕒 30 min

---

🚀 How to use

1. 📝 Sign up. Create a free account with $5 credit (takes 2 minutes).
2. 🤖 Create a Slack bot. Set up a bot with scopes: channels:read, groups:read, chat:write, users:read.
3. 🌐 Deploy in standby. Run the Actor so it listens for MCP requests.
4. 🚀 Send MCP payloads. POST to /mcp?token=YOUR_APIFY_TOKEN with your bot token and method.
5. 📥 Connect your AI. Point your MCP-enabled copilot (Cursor, Claude, custom agent) at the endpoint.

⏱️ Total time: 15 minutes from token creation to first automated Slack reply.

---

💼 Business use cases

🎫 Support & Operations Triage tickets with AI reading last 200 messages Escalate threads with logged next steps Generate daily digest summaries automatically Broadcast policy updates across teams

📊 Revenue & Platform Summarize renewal risks from private channels Route opportunities into CRM follow-ups Spin up project channels with member lists Monitor tool usage and billing per event

---

🔌 Automating Slack MCP Server

• 🟢 Node.js. Install the apify-client NPM package.
• 🐍 Python. Use the apify-client PyPI package.
• 📚 See the Apify API documentation for full details.

---

❓ Frequently Asked Questions

---

🔌 Integrate with any app

• Make - Automate Slack workflows
• Zapier - Connect 5,000+ apps
• Slack - Native Apify-Slack integration
• Airbyte - Data pipelines
• GitHub - Trigger from commits
• Google Drive - Export to Drive

---

🔗 Recommended Actors

• 🏢 HubSpot Marketplace Scraper - SaaS partner data
• 📰 PR Newswire Scraper - Press releases for Slack alerts
• 💼 DealStream Scraper - Business listings
• 🏪 BizQuest Scraper - SMB sale opportunities
• 🚗 Bring A Trailer Scraper - Auction updates

💡 Browse the complete ParseForge collection.

---

🆘 Need Help? Open our contact form to request a new scraper or report an issue.

---

⚠️ Disclaimer: Independent tool, not affiliated with Slack Technologies, LLC or any of its subsidiaries. All trademarks mentioned are the property of their respective owners.