Orchestrator MCP server for sending batches of tasks to agent sessions
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"crow-orchestrator-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# crow-orchestrator-mcp Orchestrator-only delegation tool. Loaded **in addition to** [`crow-task-mcp`](../crow-task-mcp) by orchestrator agents; not loaded by workers. ## Tools | Tool | Backend ext_method | Purpose | |------|-------------------|---------| | `task_send` | `_task/send` | Delegate a batch of tasks to another session. Populates the target's task list, records the caller, and kicks off the target's task loop. On normal completion the backend sends a canned message back to the caller telling it to `query_memory` for the target's final summary. | ## Why a separate server `task_send` is a delegation capability — it sets up a completion callback (`set_caller` + `notify_caller_done`) and spawns the target's task loop. Only orchestrators should advertise it. Keeping it out of `crow-task-mcp` means: - workers don't get a delegation tool they shouldn't use - no duplicate `task_send` schema when an orchestrator loads both servers Orchestrator agents load **both** servers: - `crow-task-mcp` → `send_prompt`, `task_read`, `task_write` (manage own session) - `crow-orchestrator-mcp` → `task_send` (delegate to others) ## Architecture Schema-only definition for the LLM (`raise NotImplementedError`). Real execution: `react.py` → `execute_orchestration_task_send` in `tools.py` → `conn.ext_method(method="task/send")` → sidex client → `sidex-acp` backend (`orchestration_3.rs::task_send`). ## Run ```bash uvx crow-orchestrator-mcp ```
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.