Skip to main content
Glama
JBrightmanAI

git-intel

by JBrightmanAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to git-intel

No user-submitted related servers found.

    Related Servers

    • GitIntel

      hoangsonww
      A
      license
      A
      quality
      A
      maintenance
      A local Git intelligence MCP server that provides deep repository analytics including hotspots, temporal coupling, knowledge maps, churn analysis, and risk scoring for AI agents.
      12
      12
      MIT

    • git-intel-mcp

      s-zaid-13
      F
      license
      Not graded
      quality
      C
      maintenance
      A lightweight MCP server that analyzes Git repository history and provides insights through AI-compatible tools. It supports hotspot detection, contributor analysis, and code churn tracking.
      -

    • git-summary-mcp

      yifanyifan897645
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI assistants deep understanding of your local Git repositories, providing instant repo overviews, change summaries, blame analysis, changelogs, branch health checks, and history search.
      23 npm
      MIT

    • Git Forensics MCP

      davidorex
      A
      license
      B
      quality
      D
      maintenance
      A specialized MCP server for in-depth analysis of git repositories, offering tools for branch overview, time period analysis, file changes, and merge recommendations.
      4
      7
      Apache 2.0
    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

    A4.2/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct analytical dimension such as change frequency, code churn, file coupling, contributor ownership, complexity trends, risk assessment, release notes, contributor stats, file history, code age, commit patterns, and branch risk. While some tools touch on contributor or file history, their outputs and use cases are clearly distinct.

    Naming Consistency5/5

    All tool names follow a consistent lower-case snake_case noun pattern, using either single words (e.g., hotspots, churn) or compound nouns (e.g., knowledge_map, risk_assessment). No mixed conventions or vague action verbs are present, making the set predictable.

    Tool Count5/5

    12 tools fall comfortably within the ideal 3-15 range for a focused domain. Each tool addresses a specific repository analytics need without unnecessary overlap, making the set well-scoped.

    Completeness4/5

    The tool set covers a comprehensive range of repository intelligence, including hotspots, churn, coupling, ownership, complexity, risk, release notes, contributor analytics, file history, code age, commit patterns, and branch health. Minor gaps such as a general repository summary exist, but core analytical workflows are well covered.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources