ddflow MCP Server

What the code does

We read the source, 1 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    if Path("/.dockerenv").exists() or Path("/run/.containerenv").exists():

    db = os.path.join(root, f"probe-{mode}.db")

    return subprocess.run(["git", "-C", str(cwd), *a], capture_output=True, text=True)

            body = marshal.loads(payload)  # nosec B302

        shell=True,  # nosec B602 B604 -- the operator's configured shell line

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add ddflow-mcp -- uvx ddflow-mcp

{
  "mcpServers": {
    "ddflow-mcp": {
      "command": "uvx",
      "args": [
        "ddflow-mcp"
      ]
    }
  }
}

[mcp_servers.ddflow-mcp]
command = "uvx"
args = ["ddflow-mcp"]

{
  "mcpServers": {
    "ddflow-mcp": {
      "command": "uvx",
      "args": [
        "ddflow-mcp"
      ]
    }
  }
}

{
  "servers": {
    "ddflow-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "ddflow-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: DDFLOW_REPO (Repository root ddflow manages. Defaults to the client's working directory, resolved to the primary checkout even when called from inside a git worktree), DDFLOW_AGENT (Stable identity for this agent. Shards the event log so concurrent agents never write the same file. Defaults to host plus the git worktree's name, so every process in one worktree agrees and two parallel agents differ. A harness running SEVERAL agents inside one worktree must set this, or their work merges into a single identity).