Slack
readSlackThread
Read Slack Thread
Read a Slack thread from a bridged channel into context.
Ask Claude, ChatGPT, Cursor or any AI connected to The Cloud "read that Slack thread", and it calls readSlackThread.
Example call
The MCP tools/call params, with the required arguments only.
{
"arguments": {
"channel": "<channel>",
"space": "<space>",
"threadTs": "<threadTs>"
},
"name": "readSlackThread"
}Arguments
channelstringrequiredThe channel id or name (must be authorized on the bridge)spacestringrequiredThe Space whose bridge to use: a pageSpace id or slug (from listPageSpaces), or a team idthreadTsstringrequiredThe Slack thread timestamp (ts) of the root message
Returns
The registry does not declare a return shape.
Ask for it
The Cloud routes these requests to this verb.
- read that Slack thread
- what was said in #ext-teka
Pair it with
The verbs that finish the job.
Questions
What does readSlackThread do?
Read a Slack thread from a bridged channel into context. It is one of the tools The Cloud MCP server gives every connected AI.
How do I use readSlackThread from Claude or ChatGPT?
Connect your AI to The Cloud at https://mcp.thecloud.so/mcp and sign in once. Then ask Claude, ChatGPT, Cursor or any AI connected to The Cloud "read that Slack thread", and it calls readSlackThread.
Is readSlackThread safe to let an AI call?
readSlackThread is read-only: it changes nothing. It reaches a system outside The Cloud on your behalf.
Connect
One endpoint gives your AI this tool and every other one: connect Claude, ChatGPT, Cursor or Gemini, read what The Cloud is, or see pricing.