Worktree Orbit Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 30, 2026

Aggregate local Git worktree topology without exposing repository content. Tools include inspect...

VerifiedSTDIODesktop onlyFiles & StorageDeveloper Tools

Overview

AI-generated overview

Local MCP server that reports aggregate Git worktree topology for a repository, such as counts, clean/dirty state and lock or prunable flags, without exposing…

What you can do
  • Inspect worktree topology for a repository: aggregate worktree count, primary and linked counts, clean or dirty counts, detached, locked and prunable states, plus a coarse topology hint.
  • Results are aggregate signals only; no paths, branch names, hashes, remotes, lock reasons, subjects, authors or file contents are returned.
When to use it
Useful when you keep several Git worktrees alive at once and want an assistant to tell you whether a repository has parallel worktrees, whether they are clean, and whether detached, locked or prunable worktrees need attention.
Requirements
Runs as a local process over stdio, installed from the npm package and started with Node.js after a build step. The selected repository must stay inside the WORKTREE_ORBIT_ROOT environment variable. Local Git commands are used; no network access.
Before you install
Read-only by design: it does not add, remove, move, lock, unlock, reset, prune or modify worktrees. Results are aggregate signals, not a substitute for inspecting a specific worktree before deleting it. Status checks are bounded and time limited.

Installation

In SourceWeft

  1. Open Worktree Orbit Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

worktree-orbit-mcp

Worktree Orbit is a local MCP for developers who keep several Git worktrees alive at once. It answers whether a repository has parallel worktrees, whether they are clean, and whether detached, locked, or prunable worktrees need attention.

Tool

  • inspect_worktree_topology: returns aggregate worktree count, primary and linked counts, clean or dirty counts, detached state, lock state, prunable state, and a coarse topology hint.

It never returns paths, branch names, hashes, remotes, lock reasons, subjects, authors, or file contents.

Safety

  • Local Git commands only. No network access is used.
  • The selected repository must stay inside WORKTREE_ORBIT_ROOT.
  • Commands are read-only: the server does not add, remove, move, lock, unlock, reset, prune, or modify worktrees.
  • Worktree status checks are bounded and time limited.
  • Results are aggregate signals, not a replacement for inspecting a specific worktree before deleting it.

Run

bash
npm installnpm run buildnode dist/index.js

Source: README.md at commit 7330cc2

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.