reply_thread — Slack MCP by Nova (CIVAI) MCP Tool
reply_thread
(reply thread) is one of 19 tools on the
Slack MCP by Nova (CIVAI)
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call reply_thread from your client
- Claude Code Slack MCP by Nova (CIVAI) reply_thread run in your project directory
- Claude Desktop Slack MCP by Nova (CIVAI) reply_thread ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Slack MCP by Nova (CIVAI) reply_thread ~/.cursor/mcp.json
- VS Code Slack MCP by Nova (CIVAI) reply_thread .vscode/mcp.json
- Zed Slack MCP by Nova (CIVAI) reply_thread ~/.config/zed/settings.json
- Windsurf Slack MCP by Nova (CIVAI) reply_thread ~/.codeium/windsurf/mcp_config.json
- Cline Slack MCP by Nova (CIVAI) reply_thread ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Slack MCP by Nova (CIVAI) reply_thread ~/.gemini/settings.json
- Grok Slack MCP by Nova (CIVAI) reply_thread .mcp.json (in your project root)
- ChatGPT Slack MCP by Nova (CIVAI) reply_thread Settings → Connectors → Advanced → Developer mode
- Claude.ai Slack MCP by Nova (CIVAI) reply_thread Settings → Connectors → Add custom connector
- LangChain Slack MCP by Nova (CIVAI) reply_thread pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp-slack_android https://nova.civai.co/mcp/agents/mcp-slack_android
Other tools on this server
- session_status
- list_channels
- channel_info
- list_channel_members
- list_workspace_users
- search_people
- post_message_rich
- thread_replies
- delete_message
- post_message
- conversation_history
- open_conversation
- create_channel
- user_boot
- list_workspaces
- confirm_email_signin
- get_network_identity
- set_network_identity
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.