If you're referring to the MCP server published by this repository, it's **herdr-inbox** (the README calls it “herdr inbox”).
**Description:** It lets Claude Code agents running in herdr ask a question once, get a receipt, and keep working instead of blocking, while the operator answers all open questions from a single popup and each answer is delivered back to the pane that asked.
A couple of notes on the constraints you gave:
- The name used is the repository's own project name, **herdr-inbox**, not a person or organization.
- The description deliberately avoids repeating the name and focuses on what the server enables: asynchronous agent questions, non-blocking work, centralized answering, and delivery back to the originating agent.
- If you want the answer as a strict JSON object only, it would be:
```json
{
"name": "herdr-inbox",
"description": "Enables Claude Code agents running in herdr to ask a question once, receive a receipt, and continue working instead of blocking, while the operator answers all open questions from one popup and each answer is delivered back to the pane that asked."
}
```
Alternatives to If you're referring to the MCP server published by this repository, it's **herdr-inbox** (the README calls it “herdr inbox”).
**Description:** It lets Claude Code agents running in herdr ask a question once, get a receipt, and keep working instead of blocking, while the operator answers all open questions from a single popup and each answer is delivered back to the pane that asked.
A couple of notes on the constraints you gave:
- The name used is the repository's own project name, **herdr-inbox**, not a person or organization.
- The description deliberately avoids repeating the name and focuses on what the server enables: asynchronous agent questions, non-blocking work, centralized answering, and delivery back to the originating agent.
- If you want the answer as a strict JSON object only, it would be:
```json
{
"name": "herdr-inbox",
"description": "Enables Claude Code agents running in herdr to ask a question once, receive a receipt, and continue working instead of blocking, while the operator answers all open questions from one popup and each answer is delivered back to the pane that asked."
}
```
MCP server that enables Claude Code to communicate with other Claude Code agents over HTTP, allowing users to ask questions about remote codebases or delegate coding tasks.
MCP server for inter-agent communication. Gives multiple Claude Code sessions a shared message board, agent registry, and orchestration layer — backed by a cloud relay so agents can coordinate across machines, repos, and teams.
MCP server that provides cross-session awareness for Claude Code, tracking active sessions, file conflicts, and shared todos to enable agent coordination without blocking tool calls.
MCP server that enables Hermes Agent to delegate development tasks to Claude Code CLI, reusing the Claude Code subscription without additional API costs.