repo-pulse-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REPO_PULSE_REPOS | Yes | The repository allowlist: absolute paths to the local git repositories to serve, separated by ':' on macOS/Linux or ';' on Windows (e.g. ~/code/my-app:~/code/my-lib). This is equivalent to passing repeated --repo CLI arguments. Only repositories listed here are served, and the server refuses to start if no repository is configured. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recent_activityA | List commits on HEAD from the last N days, newest first. Optionally filter by author (case-sensitive substring of the author name) and/or a repository-relative path. |
| commit_searchA | Search commit messages (subject and body) on HEAD for a literal, case-insensitive text, newest first. Useful for finding when and why something changed, e.g. a ticket id, a feature name or "revert". Optionally limited to a time window, author and/or path. |
| file_historyA | List the commits on HEAD that changed a single file, newest first, following the file across renames. Each commit includes the path it had then and lines added/removed. Useful for "how did this file evolve?" and "who reworked it, and when?". |
| file_hotspotsA | Rank files by how many commits changed them in the last N days (merge commits excluded). Useful for spotting churn, risky areas and refactoring candidates. |
| change_couplingA | Find pairs of files that are often changed in the same commits in the last N days (merge commits excluded), most shared commits first. Reveals hidden dependencies that imports do not show, e.g. code and the config or test it always drags along. Pass "file" to see what usually changes together with one file. |
| list_tagsA | List tags (releases) newest first with their date and tagged commit, plus the latest tag reachable from HEAD and how many commits were made since it (unreleased work). Use it to find tag names for release_notes_draft or compare_refs. |
| release_notes_draftA | Group commits between two refs by conventional-commit type (breaking changes, features, fixes, ...) and return both structured sections and a Markdown draft. "from" defaults to the latest tag before "to"; without any tag, all commits up to "to" are used. To draft notes for an existing release, pass its tag as "to" (see list_tags). |
| compare_refsA | Compare two refs (branches, tags or commits): how many commits "head" is ahead of and behind "base", and which commits those are, newest first. Useful for "how far behind main is my branch?" or "what is on this branch that is not released yet?". |
| stale_branchesA | List branches whose latest commit is at least N days old, oldest first, and whether each is already merged into HEAD. |
| contributor_summaryB | Count commits per author on HEAD in the last N days, most active first. Optionally restricted to a path. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weekly_engineering_update | Draft a weekly engineering update for stakeholders from recent repository activity. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| app overview | Current branch, last commit, latest tag and commit/branch/tag counts. |
TDQS
Scored across 10 tools
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.
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.
10 tools is well within the ideal range and each earns its place in the analytics workflow. No obvious redundancy or bloat.
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.