# rusq/slackdump

Save or export your private and public Slack messages, threads, files, and users locally without admin privileges.

Repository: https://github.com/rusq/slackdump
Canonical: https://ross.abutalabs.com/products/slackdump
Language: Go
License: AGPL-3.0
License Family: copyleft
Topics: slack, archive, dumper, dump, channels, mattermost, slackdump, migration-tool, backup, slack-exports, mattermost-app, mcp-server
Last push: 2026-08-19T09:15:10+00:00

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 98, release rhythm 98, longevity 100
- inputs: {"age_days": 1767, "days_push": 14, "days_rel": 14, "gap_med": 9, "n_releases_24m": 50}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2764, forks 155 (observed 2026-08-28T04:07:18.554983+00:00)

## What it is
Slackdump is a Go CLI tool that archives private and public Slack messages, threads, files, users, channels, and emojis locally without requiring admin privileges. It can generate Slack Export archives, incremental backups, SQLite archives, and exposes an MCP server for AI agent access to Slack data.

## Use cases
- export my private Slack conversations without admin access
- archive Slack channels on a free plan before the 90-day message limit
- create a Slack Export archive for Mattermost migration
- back up Slack messages and files locally
- download Slack emojis and custom reactions
- search archived Slack messages offline
- give an AI agent access to my Slack history via MCP

## When to choose
- you need to preserve Slack history without workspace admin rights
- you're on a free Slack plan with message history limits and want incremental archives
- you're migrating from Slack to Mattermost and need a compatible export
- you want local, privacy-respecting Slack data extraction instead of third-party cloud tools

## When to avoid
- you have full admin access and prefer official Slack compliance exports
- your organization's policies or Slack terms prohibit automated scraping
- you need a hosted SaaS backup solution rather than a local CLI tool
- you only need to read public Slack data via a bot app rather than dump archives

## Facets
- artifact type: cli-tool
- maturity: active
- function: backup, web-scraping, search-engine, mcp, developer-tools, cli, file-system, data-science
- domain: messaging-platforms, self-hosted, files, developer-tools, privacy
- platform: windows, cli, go, cross-platform
- tags: slack-export, slack-archive, mattermost-migration, no-admin-privileges, emoji-download, sqlite-archive, incremental-backup, mcp-server, automation, data-engineering, linux, macos

## Member repositories
- rusq/slackdump (main) score 98

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:18.554983+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T08:16:47.500352+00:00, confidence not recorded.
  - readme: https://github.com/rusq/slackdump (fetched 2026-08-28T04:07:18.554983+00:00, sha f7d28fb2dbf8)
- Data as of 2026-08-30T08:39:29.467469+00:00.