Do I need Slack admin rights or an API token?

No. slack_list_channels reads the local Slack cache already on your Mac, so there are no tokens, OAuth scopes, or admin approvals required. If you can open Slack, the tool can list your channels.

Does it include private channels and DMs?

Yes. The tool returns public channels, private channels, and direct messages (DMs) that exist in your local Slack cache, so the AI sees the same channel list you do.

Is my Slack data sent to the cloud?

No. LMCP runs entirely on your Mac and reads the cache locally. Your channel list is never uploaded or stored on any server — it's passed directly to your AI client over a local connection.

List Slack Channels with AI on Mac — slack_list

slack_list_channels lets your AI assistant pull a full inventory of your Slack workspace straight from your Mac. It lists public channels, private channels and direct messages (DMs) by reading the local Slack cache on your machine — no Slack admin token, no bot setup, nothing fetched from Slack's servers. You just ask in plain language. For example, type: "List all my Slack channels and show which ones are private." and the assistant returns the complete set, grouped by type.

Because it reads the on-disk cache, it works with the same Slack you already use every day. No reconnecting, no OAuth scopes, no waiting on a workspace admin to approve an integration.

Which AI agents work?

LMCP exposes slack_list_channels to every major AI client:

Desktop clients — Claude Desktop, Cursor, VS Code (GitHub Copilot), Windsurf and Zed auto-configure over a local stdio connection. Install LMCP, restart the client, and the tool appears.
Web AIs — Claude.ai (web), ChatGPT, Grok and Perplexity connect through the LMCP Cloud Relay connector, which securely bridges the web assistant to the LMCP server running on your Mac.

The same 150+ tools are available across all of them, so the channel list you get in Claude Desktop is identical to the one in Cursor or ChatGPT.

Automation

Listing channels is rarely the end goal — it's the lookup step that feeds everything else. Your AI can chain slack_list_channels with other tools to do real work:

Find the right channel ID, then post or read messages in it.
Map a teammate's DM, then summarize your recent conversation with them.
Identify all private channels you belong to before drafting a status update across teams.
Cross-reference Slack channels with your Calendar or Mail so the AI knows which project a meeting belongs to.

Because the AI discovers the channels on its own, you don't have to copy-paste channel names or IDs — it resolves them for you.

Context

The assistant is working with your actual Slack data: your real channels, your real DM list, your real private groups. That means answers reflect your workspace, not a generic guess. Ask "Which channels haven't I checked this week?" or "Do I have a DM with Maria?" and it reasons over the genuine list pulled from your Mac's cache.

Productivity

Hunting through Slack's sidebar for the right channel — especially across multiple workspaces with dozens of private channels — burns minutes you don't notice adding up. Letting the AI enumerate and filter channels instantly turns "where do I post this?" into a one-line question. Combined with message tools, a triage that used to take five minutes of clicking becomes a single prompt, and the assistant can repeat it on demand without you touching Slack at all.

Privacy & GDPR

Everything runs locally on your Mac. LMCP reads the Slack cache that already lives on your machine and hands the result to your AI client over a local connection — no copy of your channel list is ever uploaded, stored, or sent to an LMCP server. There are no API keys to leak and no third-party cloud in the path. This is privacy by architecture, not by policy. Read more about how this makes LMCP GDPR-compliant by architecture.

Ready to try it? Download LMCP, install it, and ask your assistant to list your Slack channels in seconds.