What it can do: MCP Task Orchestrator

MCP server · jpicklyk

What MCP Task Orchestrator declares, asks for and runs, according to the marketplaces we read. Runs on your machine, in a container started from this image: ghcr.io/jpicklyk/task-orchestrator:3.16.0. Tools it declares: 42. Environment variables it asks for: 7, secrets among them: 0. As of our marketplace pass on 2026-10-12.

This is not a security audit. We list what the marketplaces publish about this plugin: what it declares, what it asks for and what it runs. We do not run or inspect its code, and a verified mark is the marketplace's statement, not ours.

Where it runs

Runs on your machine, in a container started from this image: ghcr.io/jpicklyk/task-orchestrator:3.16.0As declared on: Official MCP Registry.
Runs on your machine, in a container started from this image: ghcr.io/jpicklyk/task-orchestratorAs declared on: Docker MCP Catalog.

What it declares

Tools it declares: 42. As declared on: Docker MCP Catalog.

add_section
add_template_section
apply_template
bulk_create_sections
bulk_delete_sections
bulk_update_sections
bulk_update_tasks
create_dependency
create_feature
create_project
create_task
create_template

Show the remaining 30

delete_dependency
delete_feature
delete_project
delete_section
delete_task
delete_template
disable_template
enable_template
feature_to_markdown
get_feature
get_overview
get_project
get_sections
get_task
get_task_dependencies
get_template
list_templates
project_to_markdown
reorder_sections
search_features
search_projects
search_tasks
task_to_markdown
update_feature
update_project
update_section
update_section_metadata
update_section_text
update_task
update_template_metadata

Prompts and resources: the marketplaces we read do not publish them.

What it asks for

Environment variables it asks for: 7, secrets among them: 0. As declared on: Official MCP Registry.

AGENT_CONFIG_DIR
DATABASE_PATH
LOG_FILE
LOG_LEVEL
MCP_HTTP_PORT
MCP_TRANSPORT
USE_FLYWAY

Names only: we keep no values, examples or descriptions of these variables. OAuth scopes and install-time settings are not published by the marketplaces we read.

What it runs besides MCP

None of the marketplaces we read lists hooks, commands, agents or language servers for it.

Who answers for it

jpicklyk

No marketplace we read marks it or its publisher as verified.
License: MIT.
The repository github.com/jpicklyk/task-orchestrator belongs to the account the publisher is listed under on Official MCP Registry.

How it has changed

Its tools, settings, hooks and composition have not changed since we started watching it.

In context

Median number of secrets an MCP server asks for on the marketplaces we read: 0.0. This one asks for: 0.
Share of MCP servers that run on a remote server: 63%.

Where it is published and how its figures have moved

Compare it side by side with similar plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on 2026-10-12. We publish no contact details for plugin publishers.