Skip to main content
Glama
Sign In
git-context-mcp

git-context-mcp

by muhannad-hash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to git-context-mcp

No user-submitted related servers found.

    Related Servers

    • provenance-mcp

      claudechen95
      A
      license
      Not graded
      quality
      D
      maintenance
      Answers why code exists by tracing file:line or natural-language questions through git blame, commits, PRs, and linked issues, providing cited evidence from history.
      76 npm
      MIT

    • Selvedge

      masondelan
      A
      license
      A
      quality
      B
      maintenance
      Change tracking for AI-era codebases. AI agents call it to log structured change events (entity + diff + reasoning) before the session ends, then query history with diff, blame, history, changeset, and search. Captures the intent that would otherwise evaporate.
      8
      188 PyPI
      26
      MIT

    • infernoflow

      ronmiz
      A
      license
      B
      quality
      B
      maintenance
      Git-native memory for coding agents, so every session starts warm. Gotchas, decisions, dead ends and bookmarks are saved as plain JSONL in your repo; Claude Code, Cursor and Copilot read them, and teammates get them through git.
      9
      396 npm
      8
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: blame_context focuses on line-level authorship and rationale, commit_story provides comprehensive commit details, file_contributors shows author statistics, file_history gives recent commit timeline, and search_commits enables keyword-based discovery. The descriptions clearly differentiate their scopes and use cases.

    Naming Consistency5/5

    All tools follow a consistent snake_case naming pattern with clear, descriptive compound names (e.g., blame_context, commit_story, file_contributors). The naming convention is uniform throughout, making the tool set predictable and easy to understand at a glance.

    Tool Count5/5

    With 5 tools, this server is well-scoped for its purpose of providing Git context and history insights. Each tool serves a specific, valuable function in the domain, and the count is neither too sparse nor bloated, allowing comprehensive coverage without overwhelming complexity.

    Completeness5/5

    The tool set offers complete coverage for exploring Git history and context: from line-level blame and commit details to file authorship, recent changes, and commit search. There are no obvious gaps; agents can navigate from high-level searches to detailed investigations seamlessly, covering the full lifecycle of code changes.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources