worktree-orbit-mcp
Related Servers
Alternatives to worktree-orbit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to inspect local Git repositories through five focused, read-only tools for repository trees, literal text search, numbered file reads, bounded git diffs, and project summaries while confining paths, skipping secret-like and binary files, and enforcing output limits.MIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only inspection of Git repository status and diff summaries, along with validation of OpenTofu and Ansible configurations, through a strictly limited, non-mutating toolset.MIT
- FlicenseAqualityDmaintenanceProvides bounded, read-only analysis of local project directories, enabling inventory, marker detection, and safe file reads without executing code.4-
- AlicenseAqualityBmaintenanceEnables AI clients to interrogate a local Git repository's history, surfacing change hotspots, per-author activity, files that change together, single-file commit history, and draft changelogs between refs. It is strictly read-only, requires no API keys, and returns structured data for the client to interpret.6MIT
- AlicenseAqualityBmaintenanceEnables AI agents to safely read, search, and inspect a local git repository, including PR-style diffs and changed-file summaries. It also supports opt-in allowlisted test runs.4MIT
- AlicenseAqualityAmaintenanceRead-only server that reports what is actually true in a local Ansible checkout: the option specs of installed modules, task-argument validity checks, role interfaces, redacted inventory, play structure, effective config, requirements drift, and which tasks a collection upgrade would break. It lets coding agents verify specs and arguments against the installed collections before writing anything, without running plays, connecting to managed hosts, or supplying vault secrets.1192 npm1MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly described, making selection unambiguous.
The tool name 'inspect_worktree_topology' follows a clear verb_noun pattern in snake_case, which is consistent and predictable. As a single tool, it sets a clear convention.
The server has only one tool, which is on the low end of typical tool counts. While the narrow scope of inspection might justify a single tool, the server name suggests a broader worktree management capability, making the count feel slightly thin.
The tool provides a comprehensive inspection summary, but lacks any management operations (create, delete, prune, etc.) that the server name 'worktree-orbit' implies. This leaves significant gaps in the tool surface for full worktree lifecycle coverage.