Do I need a Slack API token or admin approval?

No. slack_list_workspaces reads from Slack Desktop's local IndexedDB cache on your Mac, so there's no token to paste, no OAuth flow and no Slack admin involvement.

Does it show all my Slack workspaces?

It lists every workspace (team) you're currently signed into in the Slack Desktop app — the same ones you see in your sidebar, including multiple companies or client orgs.

Is my Slack data sent to the cloud?

No. The tool runs entirely on your Mac and reads the local cache. No Slack data is uploaded to LMCP's servers or stored anywhere off your machine.

Which AI assistants can use this tool?

Claude Desktop, Cursor, VS Code, Windsurf and Zed connect locally via stdio, while ChatGPT, Claude.ai, Grok and Perplexity connect through the LMCP Cloud Relay connector.

List Slack Workspaces with AI on Mac — slack_list

The slack_list_workspaces tool lets your AI assistant see every Slack workspace (team) you've signed into in Slack Desktop on your Mac. It reads straight from Slack's local IndexedDB cache, so there's no token to paste, no OAuth flow and no Slack admin approval needed. Just ask your AI in plain English: "Which Slack workspaces am I connected to?" and it returns the list of teams — handy as the first step before reading channels or searching messages.

This tool ships with LMCP, a free, native macOS MCP server that gives AI assistants safe local access to your real Mac apps — 150+ tools across Slack, Mail, Calendar, Messages, Notes and more.

Which AI agents work?

Once LMCP is installed, slack_list_workspaces is available to every major AI client:

Desktop clients — Claude Desktop, Cursor, VS Code (GitHub Copilot), Windsurf and Zed auto-configure through a local stdio connection. No copy-paste setup.
Web AIs — ChatGPT, Claude.ai (web), Grok and Perplexity connect through the LMCP Cloud Relay connector, so they can reach your Mac securely from the browser.

The same tool works identically everywhere — only the connection method differs.

Automation

Listing workspaces is the natural entry point for deeper Slack workflows. Your AI can chain it with other LMCP tools: list the workspaces, pick the one you mean, then pull channels, fetch unread threads, search messages or draft a reply — all in one conversation. For example: "List my Slack workspaces, then show me unread mentions in the Engineering workspace." The AI resolves the workspace from slack_list_workspaces and feeds it into the next call automatically, so you never juggle IDs by hand.

Context

Because the data comes from your actual Slack Desktop cache, the AI works with your real teams — the same workspaces you see in the app sidebar, including multiple companies or client orgs you've joined. There's no stale demo data and no separate account to maintain. The assistant knows exactly which workspaces exist before it acts, which means fewer wrong guesses and more accurate follow-up answers.

Productivity

If you bounce between several Slack workspaces, this saves the constant context-switching of clicking through the sidebar to remember what you're signed into. Ask once and let the AI build the rest of the workflow on top — triage mentions across teams, summarize a channel, or find that one message — without leaving your chat window. What used to be several clicks and an app switch becomes a single sentence.

Privacy & GDPR

Everything runs locally on your Mac. slack_list_workspaces reads Slack's on-disk IndexedDB cache directly — no Slack token leaves your machine, no API calls hit Slack's servers, and no workspace data is ever copied to LMCP's cloud or stored on any server. The AI only sees what you ask for, in the moment you ask. This local-first design makes LMCP GDPR-compliant by architecture. Ready to try it? Download LMCP and connect your AI in minutes.