Bring Instant Messaging
to AutoGen
Learn how to connect Slack to AutoGen and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Slack MCP Server?
Connect your Slack workspace to any AI agent to automate your team communication and collaboration. Slack provides a premier platform for business messaging, and this integration allows you to retrieve channel info, send messages, and search through conversational history through natural conversation.
What you can do
- Communication Orchestration — Post instant messages to channels or direct conversations and manage team threads programmatically.
- Channel & User Management — List all available channels and retrieve detailed member profile metadata directly from the AI interface.
- Search & Discovery Intelligence — Search through messages and retrieve channel histories to stay informed on team discussions via natural language.
- Presence & Status Tracking — Access user presence metadata and monitor team availability to ensure optimal collaboration.
- Operational Monitoring — Test authentication and monitor workspace health to ensure reliable connectivity between Slack and your AI workflows.
How it works
1. Subscribe to this server
2. Enter your Slack Bot User OAuth Token (xoxb-...) from your app settings
3. Start managing your team communications from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Project Managers — quickly post updates and retrieve team discussion points without switching between channels.
- Support Teams — automate the retrieval of user details and monitor support channels via natural conversation.
- Operations Managers — streamline the delivery of notifications and coordinate team communications directly within the chat.
Built-in capabilities (11)
Verify API access
Get metadata for a channel
List recent messages
Check if a user is online
Get details for a user
List public channels
List all pinned messages in a channel
Get reactions on a specific message
List workspace members
Search for messages
Send a message to a channel
Why AutoGen?
AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Slack tools. Connect 11 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.
- —
Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Slack tools to solve complex tasks
- —
Role-based architecture lets you assign Slack tool access to specific agents. a data analyst queries while a reviewer validates
- —
Human-in-the-loop support: agents can pause for human approval before executing sensitive Slack tool calls
- —
Code execution sandbox: AutoGen agents can write and run code that processes Slack tool responses in an isolated environment
Slack in AutoGen
Slack and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Slack to AutoGen through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Slack in AutoGen
The Slack MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in AutoGen only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Slack for AutoGen
Every tool call from AutoGen to the Slack MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Slack Bot User OAuth Token?
Log in to Slack API, select your app, and navigate to OAuth & Permissions. You will find the token starting with xoxb- under the OAuth Tokens for Your Workspace section.
How does AutoGen connect to MCP servers?
Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Slack tools during their conversation turns.
Can different agents have different MCP tool access?
Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
Does AutoGen support human approval for tool calls?
Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.
McpWorkbench not found
Install: pip install "autogen-ext[mcp]"