A
licenseA
qualityB
maintenanceEnables AI agents to perform exact-match, transactional multi-file edits with atomic writes, dry-run diffs, and self-correcting error diagnostics that reduce token usage.
1
1
MIT
Turnpack
by OnlyTerp
Related Servers
Alternatives to Turnpack
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to safely inspect, edit, and test code within a bounded repository environment to solve software engineering tasks and verify fixes.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search code, inspect symbols, navigate call graphs, and analyze change impact across scoped local repositories through the same engine as the CLI and REST API.19 PyPIMIT
- FlicenseAqualityBmaintenanceEnables coding agents to inspect repository state, create and amend commits, rewrite history and manage stacked branches, worktrees, and pushes against any Git remote.10923 npm-
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable coding agents to perform batched, token-efficient file and search operations with tolerant, automatically verified edits and diffs. It supports sandboxed workspace access, optional command execution, caching, and post-edit syntax/import checks.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to retrieve focused, bounded repository context locally and read-only, reducing token usage while never modifying the repository or executing its code.-
TDQS
A3.9/5.0
Scored across 3 tools
Disambiguation3/5
ship is clearly distinct (writes + verify with rollback), but pack and batch both read/search the repo — pack does regex search plus files/glob/git status, while batch does ctx.grep/ctx.read/ctx.outline/ctx.gitStatus. The descriptions offer heuristics ('2+ files' vs 'a question that would take many reads'), but the boundary between a multi-file read and a scripted read is fuzzy and an agent could easily pick either.
Naming Consistency4/5
All three names are single lowercase words in a consistent, terse style with no case or separator mixing. The only weakness is that the words are metaphors (pack/ship/batch) that don't encode read vs. write vs. script, so the pattern is consistent but not self-describing.
Tool Count4/5
Three tools is minimal but each is a deliberate composite covering a real workflow (read-many, write-and-verify, scripted analysis), so nothing feels redundant or padded. The count is slightly thin, since some actions only exist as sub-operations of a larger tool.
Completeness3/5
Reading, editing, file creation/move/delete, and running verification commands are covered, which handles core edit loops. Notable gaps remain: no standalone command execution (without an edit), no diff or log inspection beyond git status, and no git commit/branch/stage operations, which will force agents to leave the server for common repo tasks.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues