Skip to main content
Glama
hasanyelaldi

repo-pulse-mcp

by hasanyelaldi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to repo-pulse-mcp

No user-submitted related servers found.

    Related Servers

    • gitlog-mcp

      ManiaSacha
      A
      license
      B
      quality
      A
      maintenance
      Give your AI coding agent superpowers over git history — auto-generate changelogs, analyze commits, attribute blame, and draft release notes via MCP. Zero runtime dependencies.
      6
      1
      MIT

    • mcp-git-tools

      rog0x
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to analyze local Git repositories with commit logs, diffs, blame, statistics, and branch analysis using native git commands without requiring a GitHub API.
      29 npm
      MIT

    • Local Commander

      netbka
      A
      license
      A
      quality
      A
      maintenance
      For people who want their AI to run the build, read the error and check the dev server itself, instead of pasting output into chat. Works with Claude Desktop (one-click installer), Cursor, Claude Code and Cline. Runs locally over stdio or HTTP, no telemetry. A seatbelt for everyday mistakes, not a sandbox.
      20
      MIT

    • Git Code Review MCP

      AyoubTRD
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to perform code reviews by providing access to staged files, git diffs, and repository file content. It allows users to evaluate changes and context within any local git repository before committing or pushing.
      3
      10 npm
      ISC
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool has a distinct angle: recent_activity (time-windowed commits), commit_search (message text), file_history (single-file evolution), file_hotspots (churn ranking), change_coupling (co-change pairs). There is mild conceptual overlap among the commit-listing tools, but the descriptions clearly scope each one so an agent can select correctly.

    Naming Consistency3/5

    All names use snake_case and are readable, but the convention is mixed: some are verb_noun (list_tags, compare_refs) while others are noun phrases (recent_activity, file_hotspots, change_coupling). Predictable enough but not a single consistent pattern.

    Tool Count5/5

    10 tools is well within the ideal range and each earns its place in the analytics workflow. No obvious redundancy or bloat.

    Completeness4/5

    The surface covers commit history, file churn, co-change, tags, release drafting, ref comparison, stale branches, and contributors. Minor gaps like listing all branches (only stale ones) or per-commit diff detail exist, but core repo-pulse workflows are covered.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources