MCP Task Orchestrator

MCP Task Orchestrator runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/jpicklyk/task-orchestrator:3.16.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm -e DATABASE_PATH -e USE_FLYWAY -e AGENT_CONFIG_DIR -e MCP_TRANSPORT -e MCP_HTTP_PORT -e LOG_LEVEL -e LOG_FILE ghcr.io/jpicklyk/task-orchestrator:3.16.0. It reads these environment variables: DATABASE_PATH, USE_FLYWAY, AGENT_CONFIG_DIR, MCP_TRANSPORT, MCP_HTTP_PORT, LOG_LEVEL and LOG_FILE; set them in the client's configuration for this server. Required arguments: -v.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "task-orchestrator": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "DATABASE_PATH",
        "-e",
        "USE_FLYWAY",
        "-e",
        "AGENT_CONFIG_DIR",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "MCP_HTTP_PORT",
        "-e",
        "LOG_LEVEL",
        "-e",
        "LOG_FILE",
        "ghcr.io/jpicklyk/task-orchestrator:3.16.0"
      ],
      "env": {
        "DATABASE_PATH": "<value>",
        "USE_FLYWAY": "<value>",
        "AGENT_CONFIG_DIR": "<value>",
        "MCP_TRANSPORT": "<value>",
        "MCP_HTTP_PORT": "<value>",
        "LOG_LEVEL": "<value>",
        "LOG_FILE": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect