repo-tutor-mcp
Related Servers
Alternatives to repo-tutor-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to inspect Python repositories read-only through eight MCP tools that expose symbols, cited source excerpts, import dependencies, and supported static caller relationships without importing or executing the code.MIT
- AlicenseAqualityBmaintenanceExposes read-only repository scanning across architecture, security, performance and product lenses, citation verification of findings against a working tree or git revision, and HTML/SARIF/Markdown dossier rendering as MCP tools for assistants such as Claude and Cursor.31Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables LLMs to analyze Python repositories structurally via AST and call graphs, providing code search, symbol lookup, change-impact analysis, workflow tracing, and explanation without embeddings.1-
- AlicenseNot gradedqualityCmaintenanceProvides coding agents with read-only MCP tools to search Python repositories, retrieve size-bounded cited source context, analyze dependency impact, and check index status—all via local incremental AST indexing and BM25 retrieval.MIT
- AlicenseNot gradedqualityDmaintenanceEnables deterministic static analysis of Python code, providing tools to inspect classes, functions, imports, dependencies, and more, without executing the code.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query a repository's verified semantic model, including capabilities, ownership, contracts, constraints, impact, health, and verification status, without re-deriving project facts. It exposes read-only tools for inspecting, reasoning about, and verifying the provenance-tracked surface.2Apache 2.0
TDQS
Scored across 3 tools
Each tool has a distinct output: AST inventory (scan_repository), dependency/cycle topology (inspect_topology), and lesson citation verification (verify_course). scan_repository and inspect_topology both statically read source and could be momentarily confused, but the described outputs make the boundary clear.
All three tools follow a clean verb_noun snake_case pattern (scan_repository, inspect_topology, verify_course). Consistent, readable, and predictable.
Three tools is on the thin side but fits a narrow read-only tutoring/analysis server, and each tool earns its place. A small addition (e.g. per-file or per-symbol lookup) would round it out without bloat.
The static-analysis and verification halves are covered, but there is no way to fetch a specific file/symbol's source or search the inventory, and no lesson authoring/update path (read-only by design). These are noticeable gaps for a repo-tutoring workflow.