mcp-pilotage
Related Servers
Alternatives to mcp-pilotage
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents to read and search code across many git repositories — files at any branch, tag or commit, history, diffs, blame and cross-repo search — over local paths or remote hosts like GitHub, GitLab and Bitbucket. It is read-only by construction, hiding secrets found in files and working with any MCP client over stdio or Streamable HTTP.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to search indexed local Git repositories for compatible existing projects and modules, evaluate their technical and structural fit, and copy reusable source bytes into a new target instead of regenerating them. It exposes six scoped MCP tools that return plans and safe file operations, so the agent only implements the remaining delta.1MIT
- AlicenseNot gradedqualityAmaintenancePrivacy-first, read-only repo intelligence for AI coding agents: scans local codebases and recommends MCP servers, repos, and research without sending data to the cloud.1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage local project files and Git operations through MCP tools, including file CRUD, search, Git status, recent commits, and project summaries.-
- AlicenseNot gradedqualityBmaintenanceProvides local, read-only MCP tools that expose a specified workspace's directory listing, file contents, text search, git status, and git diff to AI clients.1Apache 2.0
- 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
TDQS
Scored across 9 tools
The core tools target distinct resources: project inventory (lister_projets), single-project deep dive (decrire_projet), document content (lire_cerveau), git state (etat_git), content search (chercher_partout), filename search (trouver_fichiers). The only real overlap zone is the overview trio (apercu_ecosysteme, lister_projets, etat_git without a project), but descriptions explicitly delimit them ('plus dense que lister_projets', 'n'inclut volontairement ni l'état git') and even prescribe the ordering, so an agent can pick correctly.
Casing and language are perfectly uniform (all snake_case, French), but the convention is mixed: five tools use a verb-led pattern (lister_projets, decrire_projet, lire_cerveau, chercher_partout, trouver_fichiers) while four are noun phrases (apercu_ecosysteme, etat_git, diagnostic_pilotage, usage_ia_claude). Still highly readable and predictable in tone, but not a single consistent verb_noun scheme.
Nine tools is right in the sweet spot for a machine-wide observability server, and each covers a distinct axis (inventory, detail, docs, git, content search, path search, diagnostics, cost usage). No filler tools and no obviously missing companion tool.
The read-only 'pilotage' domain is well covered end to end: discovery, per-project detail, context docs, git status, two complementary search modes, self-diagnostics, and API cost tracking. The notable gap is generic file reading — trouver_fichiers and chercher_partout can locate a file but there is no tool to read arbitrary file contents (lire_cerveau is limited to markdown context docs), and there is no diff/history inspection beyond etat_git's commit list.