Jpicklyk Task Orchestrator
jpicklyk-task-orchestrator is a Claude Code plugin for the Build phase that adds an MCP server for persistent AI task orchestration, composable notes, and multi-agent context across sessions.
by jpicklyk · github.com/jpicklyk/task-orchestrator
Install this MCP plugin to persist tasks, notes, and multi-agent work context across Claude Code sessions without micromanaging how each agent executes.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install jpicklyk-task-orchestrator@jpicklyk/task-orchestratorBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:jpicklyk/task-orchestrator") and the paste-ready config with skillselion.get_install_config("plugin:jpicklyk/task-orchestrator").
What it does
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. Solo builders 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 indie 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.
Highlights
- 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
Why builders use it
Agent work evaporates between sessions and parallel agents step on each other because there is no shared, gated task and context store.
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.
At a glance
- Type - Plugin in AI Agents.
- Adoption - 0 installs, 177 stars, 0 votes.
FAQ
Who is jpicklyk-task-orchestrator for?
It is for indie and solo 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.
Comments
Share how you use jpicklyk-task-orchestrator, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.