Skip to main content
Glama
TamiShaks-2

git-context-mcp

by TamiShaks-2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to git-context-mcp

No user-submitted related servers found.

    Related Servers

    • codebase-doctor

      jordan-chris191
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI coding agents with structured, deterministic repository intelligence—file tree, dependencies, hotspots, and git history—via Model Context Protocol, enabling them to understand codebases without reconstructing architecture from scratch.
      91 npm
      1
      MIT

    • Sippion

      Sitten-Tokyo
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      -

    • FixMap

      aryamthecodebreaker
      A
      license
      Not graded
      quality
      A
      maintenance
      Deterministic, local-first repository context for coding agents. Maps an issue, prompt, or git diff to ranked files to read first, likely test commands, and review-risk notes—no API key required.
      21
      MIT

    • mcp-git-chronicle

      luckdevx
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI coding agents with Git repository history analysis, including churn hotspot detection, semantic file coupling, and recent context summaries through MCP tools.
      MIT

    • RepoLens MCP

      Sanjeev1412-official
      F
      license
      Not graded
      quality
      B
      maintenance
      Transforms local Git repositories into queryable, context-rich knowledge bases via AST-aware chunking and Git metadata, enabling AI assistants to search and understand codebases with semantic precision.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool describes a distinct analysis aspect: code map, project status, recent activity, risk scan, and work summary. There is slight overlap between 'recent_activity' and 'risk_scan' both mentioning 'hot' files, but the descriptions are clear enough to differentiate.

    Naming Consistency5/5

    All tool names follow a consistent pattern: two words in snake_case with a noun or adjective followed by a noun (e.g., code_map, project_status). No mixing of styles.

    Tool Count5/5

    With 5 tools, the set is well-scoped for a git analysis server. Each tool serves a distinct purpose without being too few or too many.

    Completeness3/5

    The tools cover high-level analyses like structure, status, recent changes, risk, and progress, but lack lower-level git operations (e.g., commit details, branch info, diffs). This is a minor gap for a comprehensive git context server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources