reply_in_message_thread — Human For AI MCP Tool
reply_in_message_thread
(reply in message thread) is one of 6 tools on the
Human For AI
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call reply_in_message_thread from your client
- Claude Code Human For AI reply_in_message_thread run in your project directory
- Claude Desktop Human For AI reply_in_message_thread ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Human For AI reply_in_message_thread ~/.cursor/mcp.json
- VS Code Human For AI reply_in_message_thread .vscode/mcp.json
- Zed Human For AI reply_in_message_thread ~/.config/zed/settings.json
- Windsurf Human For AI reply_in_message_thread ~/.codeium/windsurf/mcp_config.json
- Cline Human For AI reply_in_message_thread ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Human For AI reply_in_message_thread ~/.gemini/settings.json
- Grok Human For AI reply_in_message_thread .mcp.json (in your project root)
- ChatGPT Human For AI reply_in_message_thread Settings → Connectors → Advanced → Developer mode
- Claude.ai Human For AI reply_in_message_thread Settings → Connectors → Add custom connector
- LangChain Human For AI reply_in_message_thread pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http humanforai https://humanforai.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.