Give your AI agent the power to read and send messages across Slack, Discord, Teams and more
A unified, agent-friendly CLI for messaging platforms. Zero-config credential extraction from your desktop apps—no OAuth flows, no API keys, no admin approval needed. Works out of the box.
Messaging platforms only offer Bot tokens for API access—your AI agent can never act as you. Agent Messenger extracts user credentials directly from your installed desktop apps, letting your agent operate on your behalf. Bot tokens are fully supported too for server-side and CI/CD use cases.
- 🎭 Act as yourself, not a bot — Extracted user tokens let your agent operate on your behalf
- 🔑 No API keys needed — Automatically extracts credentials from your installed desktop apps
- 🌐 One interface, multiple platforms — Learn once, use everywhere (Slack, Discord, Teams)
- 🤖 AI-agent friendly — JSON output by default, perfect for LLM tool use
- 👤 Human friendly too — Add
--prettyfor readable output - ⚡ Token efficient — CLI, not MCP. Load only what you need. (Why not MCP?)
npm install -g agent-messengerOr use your favorite package manager.
This installs:
agent-slack— Slack CLI (user token, zero-config)agent-slackbot— Slack Bot CLI (bot token, for server-side/CI/CD)agent-discord— Discord CLIagent-teams— Microsoft Teams CLI
Agent Messenger includes Agent Skills that teach your AI agent how to use these CLIs effectively. Install the skill for your platform:
npx skills add devxoul/agent-messengerSee skills.sh for more details.
claude plugin marketplace add devxoul/agent-messenger
claude plugin install agent-messengerOr within Claude Code:
/plugin marketplace add devxoul/agent-messenger
/plugin install agent-messenger
Add to your opencode.jsonc:
Get up and running in 30 seconds:
# 1. Extract credentials from your Slack desktop app
agent-slack auth extract
# 2. See your workspace at a glance
agent-slack snapshot --pretty
# 3. Send a message
agent-slack message send general "Hello from the CLI!"That's it. No OAuth flows. No API tokens. No configuration files.
| Feature | Slack | Discord | Teams |
|---|---|---|---|
| Auto credential extraction | ✅ | ✅ | ✅ |
| Send / List / Search messages | ✅ | ✅ | ✅ |
| Threads | ✅ | ✅ | ✅ |
| Channels & Users | ✅ | ✅ | ✅ |
| Reactions | ✅ | ✅ | ✅ |
| File uploads | ✅ | ✅ | ✅ |
| Workspace snapshots | ✅ | ✅ | ✅ |
| Multi-workspace | ✅ | ✅ | ✅ |
| Bot support | ✅ | — | — |
⚠️ Teams tokens expire in 60-90 minutes. Re-runagent-teams auth extractto refresh. See Teams Guide for details.
- Slack Guide — Full command reference for Slack
- Slack Bot Guide — Bot token integration for server-side and CI/CD
- Discord Guide — Full command reference for Discord
- Teams Guide — Full command reference for Microsoft Teams
For AI Agents
- Give Claude, GPT, or your custom agent the ability to read and send messages
- Automate Slack/Discord/Teams workflows with simple CLI commands
- Build integrations without OAuth complexity
For Developers
- Quick message sending from terminal
- Scripted notifications and alerts
- Workspace snapshots for debugging
For Teams
- Automate standups and reminders
- Cross-post announcements to multiple platforms
- Build custom notification pipelines
Why not MCP? MCP servers expose all tools at once, bloating context and confusing agents. Agent Skills + agent-friendly CLI offer a better approach—load what you need, when you need it. Fewer tokens, cleaner context, better output.
Why not OAuth? OAuth requires an app and it requires workspace admin approval to install, which can take days. This tool just works—zero setup required. For those who prefer bot tokens (e.g., server-side or CI/CD), see agent-slackbot.
Inspired by agent-browser from Vercel Labs.
bun install # Install dependencies
bun link # Link CLI globally for local testing
bun test # Run tests
bun typecheck # Type check
bun lint # Lint
bun run build # BuildMIT
{ "plugins": [ "agent-messenger" ] }