my-pi
Related Servers
Alternatives to my-pi
- AlicenseNot gradedqualityBmaintenanceLocal-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.1MIT
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.35MIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceGives any MCP-compatible AI chat or agent a safe, model-neutral coding runtime with file read/search, structured multi-file patches, command execution, interactive sessions, and git operations, all confined to a single workspace and gated by permission modes.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceLocal-first code intelligence MCP server that enables coding agents to search code, inspect structure, read exact ranges, and explore Git history with explicit token budgets.23Apache 2.0
- AlicenseNot gradedqualityAmaintenanceGives MCP-compatible AI clients safe, hands-on access to local codebases: file reading/search, multi-file patches, command execution, interactive sessions, Git inspection, and coordination of local agent providers such as Antigravity and OpenCode.18Apache 2.0
- FlicenseNot gradedqualityCmaintenanceSecure local development platform that exposes controlled developer capabilities (FS, Git, search, command execution) to AI assistants via MCP with deny-by-default security and audit logging.-
- AlicenseCqualityAmaintenanceLocal-first codebase intelligence engine providing AI coding agents with a typed MCP toolset for understanding and navigating code repositories.10052Apache 2.0
- FlicenseCqualityCmaintenanceA security-first MCP server that provides LLMs with structured tools for filesystem, process, search, build/test/lint, IDE integration, and more.402-
TDQS
Scored across 13 tools
Each tool maps to a distinct resource/action: filesystem stat/read/write/patch, text vs structural search, VCS status/diff, and LSP status/diagnostics/symbols/navigate. Overlaps like fs_stat vs fs_read and search vs ast_search are resolved by clear descriptions.
All tools use snake_case, but suffixes mix nouns and verbs (workspace_info, vcs_status vs fs_read, ast_search, lsp_navigate). The prefix-based grouping is predictable, so mostly consistent with minor deviations.
13 tools is well-scoped for a workspace/code-intelligence server, covering file ops, search, VCS, and LSP without obvious redundancy. Each tool appears to earn its place.
Core read/write/patch/search/VCS/LSP workflows are covered, but there is no explicit delete/move/rename for files and VCS is limited to status/diff. These are minor gaps workable around for an inspection/editing agent.