Jpicklyk Task Orchestrator
- 197 repo stars
- Updated July 27, 2026
- jpicklyk/task-orchestrator
jpicklyk-task-orchestrator is a Claude Code plugin that adds an MCP server for persistent AI task orchestration, composable notes, and multi-agent context across sessions.
About
jpicklyk-task-orchestrator is a Claude Code plugin that registers a light-touch MCP task orchestration server built for AI agents that need durable work tracking and shared context. developers juggling multiple Claude sessions or parallel agents can define planning floors through composable notes, enforce optional gating when a step must be complete before the next, and store decisions so tomorrow’s session does not start from zero. It deliberately avoids prescribing agent tactics—your skills and prompts still drive execution—while the server keeps tasks, workflows, and session memory aligned. It fits SaaS and internal tool projects where agent-heavy builds, reviews, and ops fixes all look like a chain of tracked tasks rather than one-off chats. Install when you outgrow sticky notes in markdown and want a schema-aware orchestration layer that plays nicely with MCP, hooks, and project-management-style visibility without adopting a heavyweight PM suite.
- Light-touch MCP task orchestration with persistent work tracking across sessions and agents
- Composable notes define planning floors with optional gating transitions between workflow steps
- Schema-aware, note-driven coordination without prescribing how each agent completes work
- Hooks and skills integration keywords for workflow automation in Claude Code
- Single-plugin bundle from jpicklyk/task-orchestrator MCP server project
Jpicklyk Task Orchestrator by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
/plugin install jpicklyk-task-orchestrator@jpicklyk/task-orchestratorAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 197 |
|---|---|
| Last updated | July 27, 2026 |
| Repository | jpicklyk/task-orchestrator ↗ |
What it does
Install this MCP plugin to persist tasks, notes, and multi-agent work context across Claude Code sessions without micromanaging how each agent executes.
Who is it for?
Best when you're running Claude Code with multiple agents or long-horizon projects and want MCP-native task boards and note-driven gates without a rigid methodology imposed on the agents.
Skip if: Skip if you only need a one-shot code edit in a single chat and do not want to run or maintain an MCP orchestration server.
What you get
After you add the plugin and connect the MCP server, tasks, notes, and gating state persist so agents resume coordinated work without re-scoping from scratch.
- Registered MCP task orchestration endpoint usable from Claude Code
- Persistent tasks, composable notes, and optional gating transitions across agent runs
- Shared multi-agent execution context without replacing your existing skills
By the numbers
- Plugin bundle lists 1 plugin from repository jpicklyk/task-orchestrator
- Catalog metadata references 177 GitHub stars for the source repo
- Described as note-driven, schema-aware orchestration with hooks and skills keywords
Recommended Plugins
0pg Cc MarketplacePersonal Claude Code plugins collection
1shot Labs Squadron Comms PluginVoice communication system with ElevenLabs TTS for multi-agent coordination in Claude Code3
23blocks Os Ai MaestroAI Agent Orchestrator with Skills System - Give AI Agents superpowers: memory search, code graph queries, agent-to-agent messaging.733
3commas Io Commas ClaudeThis is a repo with shared agents and skills used company-wide4
884js Agent Plugins1 plugin
A5c Ai BabysitterBabysitter enforces obedience to agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration1.6kHow it compares
MCP task-orchestration server plugin, not a single prompt skill or a full project-management SaaS.
FAQ
Who is Jpicklyk Task Orchestrator for?
It is for developers using Claude Code who need persistent tasks, notes, and multi-agent coordination via MCP across many sessions.
When should I use Jpicklyk Task Orchestrator?
Use it when agent work spans days or multiple agents and you want composable planning notes, optional gating, and durable context instead of restarting threads.
How do I add Jpicklyk Task Orchestrator to my agent?
Install the Claude Code plugin from the bundle, configure the task-orchestrator MCP server per the repo README, then expose its tools to Claude Code in your MCP settings.