Slackdump
Slack export without admin rights and a local MCP server: the agent analyzes your messages, threads, files and users
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Exports Slack data; respect the workspace policy
- Acts on your behalf with your Slack permissions
Install
Manual install
brew install slackdumpA binary is also available in releases. First archive the conversations you need.
This is third-party code. Review the repository files before installing.
What it does
Slackdump saves your private and public Slack messages, threads, files and user list locally without admin privileges. It can dump individual conversations, run a full Slack-format export, resume an archive and store emojis. For agents there is a local MCP server over stdio or HTTP: connecting it to Opencode, Claude or another MCP client lets the agent analyze the saved Slack data. It has database tools: merge archives, remove duplicates and clean up unfinished sessions. The data stays with you, with no third-party services.
Who it is for. For people who want to save and analyze their Slack data locally, without an admin or third-party services.
Good fit when
- You need to save private or public Slack conversations without admin rights
- You want the agent to analyze your Slack archive over MCP
- You need to export channels from a free no-archive plan
Not a fit when
- Exporting data violates your Slack workspace policy
- You only need to view in Slack without a local archive
Example request
Find the release discussion in my Slack archive and compile the decisions madeLimitations
Slackdump acts on your behalf with your Slack permissions, so respect the workspace policy and data laws. The MCP needs a saved archive; an empty one shows nothing. The tool is a Go CLI, and the MCP server is started by its command and runs locally.
How to disable. Remove the slackdump entry from the MCP client config and delete the slackdump binary.
MCP
- Transport
- stdio, http
- Authentication
- not required
Security check
- Exports Slack data; respect the workspace policy
- Acts on your behalf with your Slack permissions
README in short
The README describes Slackdump as a tool for locally saving and exporting Slack messages, threads, files and users without admin rights. Modes include dumping individual conversations, a full Slack-format export, resuming an archive, a local MCP server for working with AI agents and database tools: merge, dedupe and cleanup. The MCP server runs over stdio or HTTP and works with Opencode, Claude and other clients. It is a Go CLI installed via Homebrew or a binary. AGPL-3.0 licensed.
FAQ
Do I need Slack admin rights?
No. Slackdump acts on your behalf with your permissions, but respect the workspace policy.
How does the agent analyze the data?
Through a local MCP server over stdio or HTTP connected to Opencode, Claude or another MCP client, working with your saved archive.
Related
A self-hosted knowledge base with block-level references and a built-in MCP server for connecting AI agents to your notes
A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more
Local search over Markdown notes, docs and meeting transcripts: keywords, semantic search and reranking, with an MCP server
A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI