Human-in-the-Loop

Allows AI assistants to ask questions to humans via Discord.

An MCP (Model Context Protocol) server that allows AI assistants to ask questions to humans via Discord.

This MCP server is used when AI assistants need human input or judgment during their work. For example:

- When having an LLM create documentation, the AI designs the structure while humans provide specific content
- When the AI needs confirmation on uncertain decisions
- When specialized knowledge or personal information is required

- Rust (1.70 or higher)
- Discord account and bot
- MCP-compatible AI client (Claude Desktop, Copilot Edits, etc.)
- Go toDiscord Developer Portal
- Create a new application
- Create a bot in the Bot section and obtain the token
- Set required permissions:

cargo install --git https://github.com/KOBA789/human-in-the-loop.git

{ "mcpServers": { "human-in-the-loop": { "command": "human-in-the-loop", "args": [ "--discord-channel-id", "channel-id", "--discord-user-id", "user-id" ], "env": { "DISCORD_TOKEN": "your-discord-bot-token" } } } }

For Claude Code (claude.ai/code), add to your MCP settings:

{ "mcpServers": { "human-in-the-loop": { "command": "human-in-the-loop", "args": [ "--discord-channel-id", "channel-id", "--discord-user-id", "user-id" ] } } }

Set the Discord token as an environment variable before running Claude Code:

export DISCORD_TOKEN="your-discord-bot-token" claude

Note: The server automatically reads the Discord token from theDISCORD_TOKENenvironment variable. You can also pass it via--discord-tokenargument if needed.

AI assistants can ask questions to humans using theask_humantool:

Human: Please create a documentation outline. You can ask the human as you need. Assistant: I'll create a documentation outline. Let me ask you some questions first. [Uses ask_human tool]

The AI posts questions in Discord and mentions the specified user. When the user replies in Discord, the response is returned to the AI.
- AI assistant calls theask_humantool
- MCP server creates a thread in the specified Discord channel (or uses existing thread)
- Posts the question and mentions the specified user
- Waits for user's reply
- Returns the reply content to the AI assistant
- Enable Developer Mode in Discord (Settings → Advanced → Developer Mode)
- Right-click on channel → "Copy ID"
- Right-click on user → "Copy ID"

- Future Migration to MCP Elicitation: Once MCP's Elicitation implementation becomes more widespread and standardized, we plan to migrate the UI from Discord to native MCP Elicitation. This will provide a more integrated experience directly within MCP-compatible clients.

An MCP server client for the Agent-to-Agent (A2A) protocol, enabling LLMs to interact with A2A agents.

A bridge server connecting Model Context Protocol (MCP) with Agent-to-Agent (A2A) protocol.

A bridge server connecting Model Context Protocol (MCP) with Agent-to-Agent (A2A) protocol.

Production-grade multi-agent communication MCP server with 58 tools over MCP+SSE — real-time messaging, task scheduling, shared memory, and a trust-based evolution engine. SQLite WAL persistence, 4-level RBAC, zero-dependency Python/TypeScript SDKs.

Enables room-based messaging between multiple agents.

Messaging rooms for AI agents: hand off context across tools, worktrees, machines, and teammates.

Agent-to-agent messaging platform. any MCP-compatible agent sends and receives direct messages

Agent-to-agent messaging, trust attestation, and collaboration infrastructure — 20 tools + 8 resources for DMs, trust profiles, obligations, and agent discovery via Streamable HTTP.

Enables AI assistants to request human input through a web interface, facilitating human-in-the-loop interactions.

Agent-native collaboration network: orchestrate a team of long-running agents from any MCP client, with persistent identity, real-time messaging with @mentions and threads, task handoffs, shared workspace context, semantic search, and replayable MCP App widgets.