
Slack
Post updates, read channels, and manage Slack users and apps from your agent during build and launch automation.
Overview
com.mcparmory/slack is a MCP server for the Build phase that lets agents manage Slack channels, conversations, users, and workspace apps over the Slack API.
What is this MCP server?
- Manage Slack channels and conversations programmatically
- List and administer workspace users and installed apps
- stdio MCP via mcparmory-slack on PyPI (uvx) or Docker 1.0.1
- Fits deploy notifications, support triage, and launch announcements
- From mcparmory/registry GitHub source
- Server version 1.0.1
- 2 package options: PyPI and OCI Docker
- stdio transport
Community signal: 25 GitHub stars.
What problem does it solve?
Automating Slack from your dev environment means maintaining one-off scripts instead of talking to your agent in one place.
Who is it for?
Indie builders who live in Slack for support and launches and want MCP-driven notifications and channel ops from Claude Code or Cursor.
Skip if: Teams that forbid bot tokens in dev machines, or use only email/Discord with no Slack workspace.
What do I get? / Deliverables
Once registered with valid Slack tokens, your agent can read and act on workspace communication from your IDE workflow.
- Slack-connected MCP server in your agent config
- Programmatic channel, conversation, user, and app management tools
Recommended MCP Servers
Journey fit
How it compares
Slack API MCP connector, not a copywriting or SEO distribution skill.
Common Questions / FAQ
Who is com.mcparmory/slack for?
Solo founders and small teams on Slack who want their coding agent to send messages, inspect channels, and manage workspace apps via MCP.
When should I use com.mcparmory/slack?
Use it while building integrations for alerts and bots, during Grow/support triage, or at Launch when pushing release updates to channels.
How do I add com.mcparmory/slack to my agent?
Add stdio MCP config for uvx mcparmory-slack or the Docker image, set Slack bot/user tokens and required scopes in env, then restart your client.