Task Orchestrator MCP Server

Server-enforced workflow discipline for AI agents. Prompt-based frameworks hope the LLM follows instructions. This one blocks the call if it doesn't.

People who work with ai coding assistant, context persistence and developer tools and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in Kotlin.

VERIFIED ACTIVE

LAST COMMIT 2026-09-16 · ★ 204 · #156 OF 304 MAINTAINED MEMORY · VERIFIED 2026-09-18

MIT · Kotlin · how we verify → /methodology

01 · Install Task Orchestrator

before you install - you'll need

Set TASK_ORCHESTRATOR_API_URL, MCP_TRANSPORT, API_AUTH_MODE, API_ALLOW_UNAUTHENTICATED before connecting. API_ENABLED is optional or environment-specific per the README.

Docker

docker run -i --rm ghcr.io/jpicklyk/task-orchestrator:3.14.0

Claude Desktop - add to config

{
  "mcpServers": {
    "jpicklyk-task-orchestrator": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/jpicklyk/task-orchestrator:3.14.0"
      ]
    }
  }
}

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as container (OCI image) - can be sandboxed away from your filesystem

license MIT - declared in the repository

registry namespace io.github.jpicklyk is GitHub-verified and matches the repo owner

03 · What Task Orchestrator can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Limitations (from the README)

Notes are phase-specific documentation attached to work items. An implementation agent reads a concise requirements note scoped to its task instead of scanning broader project context. Notes are keyed, role-scoped, and queryable:

Latest releases

v3.14.0 · 2026-09-16

Highlights · Added paging (limit/offset) to query_dependencies edge listings and a 1000-node cap on · graph traversal - large dependency graphs no longer blow past response limits · Added schemaWarnings to…

v3.13.1 · 2026-08-04

Changed · Adopted three retrospective improvement proposals (002fa6c6, d7662676, 4aa8d058): /implement · Step 2 gains the dedicated-worktree fallback for an unavailable/dirty main checkout; CLAUDE.md's · plugin-refresh…

v3.13.0 · 2026-07-25

> Resource/credential leasing ships in this release as a beta feature. The interfaces below are · > stable enough for evaluation and feedback, but the capability is deliberately v1-scoped - · > multi-holder admission…

04 · Who maintains Task Orchestrator

MCP Task Orchestrator is maintained by jpicklyk. It's the only MCP server we track from this author; the repo dates to May 2025.

05 · Facts

repository: github.com/jpicklyk/task-orchestrator
category: memory - ranked #156 of 304 actively-maintained memory servers as of 2026-09-18.
release cadence: 6 releases in the last 90 days (latest 2026-09-16)
registry: io.github.jpicklyk/task-orchestrator (active, first published 2026-04-15 · 3 versions)
packages: oci:ghcr.io/jpicklyk/task-orchestrator:3.14.0

06 · Task Orchestrator FAQ

What is Task Orchestrator?

Server-enforced workflow discipline for AI agents. Prompt-based frameworks hope the LLM follows instructions. This one blocks the call if it doesn't.

Is Task Orchestrator still maintained?

Yes - as of 2026-09-18, its last commit was 2026-09-16 and it shipped 6 releases in the last 90 days. We re-verify nightly.

How do I install Task Orchestrator?

Run `docker run -i --rm ghcr.io/jpicklyk/task-orchestrator:3.14.0`. The README documents 5 environment variables (TASK_ORCHESTRATOR_API_URL, MCP_TRANSPORT, API_ENABLED…) to set first. Set TASK_ORCHESTRATOR_API_URL, MCP_TRANSPORT, API_AUTH_MODE, API_ALLOW_UNAUTHENTICATED before connecting. API_ENABLED is optional or environment-specific per the README. You can also paste the ready-made client config above.

07 · Alternatives to Task Orchestrator

Alternatives to Task Orchestrator

Maintained memory servers if Task Orchestrator isn't the fit.

Pairs well with

Servers that cover what Task Orchestrator doesn't - only shown when the pairing reason fits the companion.

More memory MCP servers · Context Mem · Kage · Firekeep · Spool · Handoff