Smithery Ai Slack
Connect agents to Slack workspaces for messaging and event subscriptions so bots and workflows ship without custom Slack Bolt glue first.
Overview
ai.smithery/smithery-ai-slack is a MCP server for the Build phase that enables Slack workspace interaction and Slack event subscriptions for agents via Smithery.
What is this MCP server?
- Interact with Slack workspaces through MCP tools
- Subscribe to Slack events via MCP Resources
- Smithery streamable-http remote at @smithery-ai/slack/mcp
- Required Bearer smithery_api_key authentication header
- v1.0.0 from smithery-ai/mcp-servers slack subfolder
- Server version 1.0.0
- Supports Slack event subscription through MCP Resources per server description
- Remote URL: server.smithery.ai/@smithery-ai/slack/mcp
What problem does it solve?
Agents cannot participate in your Slack workspace or react to events until you build and host Slack API and Events API plumbing yourself.
Who is it for?
Solo builders automating Slack notifications, agent handoffs, or lightweight bots while shipping a SaaS or internal tool.
Skip if: Large orgs needing self-hosted only Slack MCP, strict data residency, or full incident/compliance workflows without reviewing Slack app permissions.
What do I get? / Deliverables
With the Smithery remote configured, your agent gains Slack MCP tools and resource-based event subscriptions during integration work.
- Slack workspace interaction tools available to the agent
- MCP Resource paths for subscribing to Slack events
- Integrated comms channel for build-time automation and notifications
Recommended MCP Servers
Journey fit
Slack MCP is a Build integration for solo builders wiring comms, notifications, and agent ops into the product they are coding. Integrations fits workspace APIs and event hooks; Grow lifecycle tools come later once the Slack bridge exists.
How it compares
Hosted Slack workspace MCP bridge, not a customer-support playbook skill or email-only comms integration.
Common Questions / FAQ
Who is ai.smithery/smithery-ai-slack for?
Solo and indie builders using AI agents who need Slack workspace actions and event subscriptions through MCP on Smithery’s hosted endpoint.
When should I use ai.smithery/smithery-ai-slack?
Use it during Build when you integrate alerts, bot replies, or agent workflows with Slack and want MCP Resources for event streams.
How do I add ai.smithery/smithery-ai-slack to my agent?
Register https://server.smithery.ai/@smithery-ai/slack/mcp as streamable-http MCP with Authorization: Bearer {smithery_api_key} and complete Slack workspace authorization per Smithery flows.