Connect Slack to Claude Desktop

Search conversations and send messages to your workspace. Add Toolspoke to Claude Desktop once and it can use 20 Slack actions. Your Slack credential stays in Toolspoke, and you choose which actions Claude Desktop may call.

Set it up in Claude Desktop

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Desktop

    Settings, then Connectors, then Add custom connector

    https://toolspoke.com/mcp

    Paste the address, then approve the request when Toolspoke asks.

  2. Install Slack and connect it

    Add Slack to a project in your Toolspoke workspace.

    Press connect and sign in to Slack. Toolspoke keeps the token encrypted and refreshes it when it expires, so there is nothing to copy and nothing to rotate by hand.

  3. Choose what Claude Desktop may do

    All 20 actions start on. Switch off any of the 10 actions that change something in Slack, and Claude Desktop gets a refusal if it tries.

What you can ask Claude Desktop for

A few of the Slack actions that only read, so they are safe to try first.

  • List channels in the workspace so you can turn a channel name into the channel ID every other action needs
  • Read recent messages from public or private channels the bot has joined, newest first
  • List workspace members so you can map user IDs seen in messages to real names
  • Build the shareable https://…slack.com/archives/… link for a specific message, so it can be quoted elsewhere

What Claude Desktop can do in Slack

10 actions read, 9 write and one deletes or permanently changes something.

Reads

  • List channels

    List channels in the workspace so you can turn a channel name into the channel ID every other action needs. Only channels the bot can see are returned; private channels additionally require the bot to be a member.

  • Read channel history

    Read recent messages from public or private channels the bot has joined, newest first. The current bot grant does not include im:history or mpim:history, so this operation cannot read DM history. Reading history does not trigger or wake an agent. Use this to catch up on a conversation; Slack caps newer apps at 15 messages per call and one call per minute, so keep the limit small and page with cursor when you need more.

  • Read thread

    Read a threaded conversation: pass the parent message's ts as thread_ts to get the parent plus every reply, oldest first. Use after read_channel_history shows a message with reply_count above zero.

  • Search

    Search messages across the workspace with Slack search syntax, e.g. "deploy in:#engineering from:@ana after:2026-01-01". This uses the user token the sign-in stored alongside the bot token. Slack's search endpoint rejects bot tokens, so fall back to read_channel_history when the grant has none.

  • List users

    List workspace members so you can map user IDs seen in messages to real names. Emails are only present when the token carries the users:read.email scope.

  • Find user by email

    Look up a single workspace member by their email address and return their user ID, which you need to mention them (<@ID>) or open a DM. Requires the users:read.email scope.

  • Get permalink

    Build the shareable https://…slack.com/archives/… link for a specific message, so it can be quoted elsewhere.

  • Get channel

    Read one channel by ID, including is_member -- whether the bot is in it. Check this before relying on posting or uploading to a channel; a bot that is not a member gets not_in_channel. If is_member is false, join a public channel with join_channel, or ask the person to /invite the bot to a private one.

  • Read list

    Read the rows of a Slack List (the board that lives as a tab in a channel), with its columns. Pass include_list (on by default) to get the column ids, types and select option ids that add_list_item and update_list_items need. Each row has an id like "Rec01..." and one field per cell. Page with cursor when response_metadata.next_cursor is set. Lists exist only on paid Slack plans, and the List must be shared with the app.

  • Get list item

    Read one row of a Slack List by its id, with every cell.

Writes

  • Send message

    Post a message to a channel, DM, or thread as the bot. Pass thread_ts to reply inside an existing thread instead of starting a new top-level message. Returns the ts of the new message, which update_message and add_reaction need.

  • Update message

    Edit a message the bot previously posted. Identify it by the channel ID and the ts returned from send_message. The bot can only edit its own messages.

  • Schedule message

    Queue a message to be posted later. post_at is a Unix timestamp in seconds and must be in the future and within 120 days. Returns a scheduled_message_id.

  • Add reaction

    Add an emoji reaction to a message, the lightweight way to acknowledge something without posting. Use the emoji's short name without colons, e.g. "white_check_mark".

  • Join channel

    Add the bot to a public channel, so it can post and upload there. Private channels cannot be joined this way -- ask the person to /invite the bot. Requires the channels:join scope.

  • Open dm

    Open (or find) the direct-message channel between the bot and one workspace member, and return its channel ID. Pass that ID to send_message or upload_file to message the person directly. Find the user ID first with find_user_by_email or list_users. Requires the im:write scope.

  • Add list item

    Add a row to a Slack List. Read the List first with read_list to learn its column ids and select option ids. Each initial_fields entry names one column_id and one value keyed by the column's type, e.g. {"column_id":"Col01","select":["OptTODO"]}, {"column_id":"Col02","user":["U0123"]}, {"column_id":"Col03","date":["2026-11-04"]} or {"column_id":"Col04","checkbox":true}. Text columns take Block Kit rich_text, not a plain string, e.g. {"column_id":"Col05","rich_text":[{"type":"rich_text","elements":[{"type":"rich_text_section","elements":[{"type":"text","text":"Fix login"}]}]}]}. Returns the new row, whose id update_list_items needs.

  • Update list items

    Change cells in a Slack List, up to 100 at once and across several rows. Each cell names a row_id from read_list, a column_id, and a value keyed by the column's type, in the same shapes add_list_item uses, e.g. {"row_id":"Rec01","column_id":"Col01","select":["OptDONE"]}. Only the cells you name change.

  • Upload file

    Upload a file to a channel, DM or thread and share it there, a PDF report, a CSV, an image. Give artifact_id for a file you created with create_artifact, or content with filename for a text file. Pass a DM channel ID from open_dm to send it to one person. At most 1 MB. Requires the files:write scope.

Deletes or permanently changes

  • Delete list item

    Delete one row from a Slack List for good. Slack keeps no undo for this through the API, so confirm the row with get_list_item first.

Slack in Claude Desktop: questions

Does Claude Desktop see my Slack credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Desktop only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Desktop from changing things in Slack?

Yes. Each of the 20 actions can be switched off for a project. Turn off the 10 that change something and Claude Desktop can only read.

Will 20 actions crowd Claude Desktop's context?

No. Toolspoke shows Claude Desktop five bridge tools, plus a guide where a toolkit has one, and Claude Desktop searches for the Slack action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Does it work in Claude on the web too?

Yes. A connector added in Settings belongs to your Claude account, so it appears in Claude on the web and in the desktop app.

What does it cost?

Tool calls are free on every plan, and a Slack call does not run in a sandbox, so it bills nothing.

Try Slack in Claude Desktop

Free to start, and tool calls cost nothing on any plan.