A Model Context Protocol server for task orchestration
Listed on its own since 2026-09-27. Until then it was part of iflow-mcp-echoingvesper-mcp-task-orchestrator, where its earlier checks remain.
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":"echoing-vesper-mcp-task-orchestrator","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.
# MCP Task Orchestrator [](https://opensource.org/licenses/MIT) [](https://www.python.org/downloads/) [](https://github.com/EchoingVesper/mcp-task-orchestrator/releases/tag/v1.8.0) A Model Context Protocol server that breaks down complex tasks into structured workflows with specialized AI roles. Features workspace-aware task management that automatically detects your project context and saves artifacts in the right locations. ## What it does - Input to Output Example **Instead of this:** ``` User: "Build a Python web scraper for news articles" Claude: [Provides a single, monolithic response with basic code] ``` **You get this structured workflow:** ``` User: "Build a Python web scraper for news articles" Step 1: Architect Role ├── System design with rate limiting and error handling ├── Technology selection (requests vs scrapy) ├── Data structure planning └── Scalability considerations Step 2: Implementer Role ├── Core scraping logic implementation ├── Error handling and retries ├── Data parsing and cleaning └── Configuration management Step 3: Tester Role ├── Unit tests for core functions ├── Integration tests with live sites ├── Error condition testing └── Performance validation Step 4: Documenter Role ├── Usage documentation ├── API reference ├── Configuration guide └── Troubleshooting guide Example Result: Structured web scraper implementation with: ✓ Error handling patterns ✓ Test coverage ✓ Documentation ✓ Development practices ``` Each step provides specialist context and expertise rather than generic responses. ## Key Features - **LLM-powered task decomposition**: Automatically breaks complex projects into logical subtasks - **Specialist AI roles**: Architect, Implementer, Debugger, Documente…
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.