Slack AI Agent
Give your team an AI agent that lives in Slack. Read channels, post updates, and run scheduled reports with Oido, self-hostable and multi-provider.
What you can automate with Slack + Oido
- Summarize a busy channel on demand and DM the digest to whoever asked.
- Post a scheduled standup prompt and collect replies into one thread.
- Watch a #support channel and escalate anything urgent to an on-call person.
- Turn a message into action, 'file this as a GitHub issue', by chaining with other MCP servers.
Oido connects to Slack through the Slack MCP server, letting your agent read channels, post messages, and react, all as native agent tools. Combined with Oido's scheduled agents, Slack becomes a place where work gets done, not just discussed.
How it works
The Slack MCP server wraps Slack's Web API as tools the agent can call directly. Oido handles auth and runs the agent either on a cron schedule or in response to events. Chain Slack with a second MCP server (GitHub, Postgres, Linear) and a single Slack message can trigger a multi-step workflow that ends back in the thread.
This is the difference between a chatbot and an operator: the agent doesn't just reply, it reads context across channels and takes real action.
Setup
Install the Slack MCP server as an Oido extension:
oido extensions install @modelcontextprotocol/server-slackOr add it directly to ~/.config/oido/mcp-servers.json:
{
"servers": {
"slack": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-slack"
],
"env": {
"SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}",
"SLACK_TEAM_ID": "${SLACK_TEAM_ID}"
},
"transport": "stdio"
}
}
}SLACK_BOT_TOKEN, Bot User OAuth token (xoxb-…) from your Slack app's OAuth settings.
SLACK_TEAM_ID, Your Slack workspace / team ID.
Confirm the exact source and env vars against the Slack MCP server, package names occasionally change.