repo-pulse
Read-only git history insights for AI: review risk, hotspots, ownership and release notes
- Pricing
- Open source
- Platforms
- CLI, self-hosted, macOS
- Runs
- Locally
- Version
- 0.6.0
- Listing updated
- today
Similar MCP servers
About repo-pulse
repo-pulse is an open-source MCP server for developer tools. It runs locally on your machine and is started by your AI client.
Repo-pulse works on local git repositories only. It runs over stdio, needs Node.js 22.12 or newer plus git, never modifies a repository and never touches the network. Pull requests, issues and CI status are explicitly out of scope, so it works the same on clones from any host or on repos with no remote.
Its 13 tools are grouped by the question they answer. For review, review_context ranks the changed files of a branch by past churn and bug fixes, flags files that usually change together but were left out, and suggests reviewers. Ownership tools estimate who knows a path, the bus factor and files whose last author has left. Release and history tools draft notes between refs, list stale branches and search commits.
Beyond tools it exposes a repo overview resource and nine prompts such as review_branch, release_notes and catch_up. All tools carry readOnlyHint, declare an output schema and return structured content plus a JSON text block. Repositories are chosen with the REPO_PULSE_REPOS variable and toolsets can be narrowed with REPO_PULSE_TOOLS.
Install
Run in a terminal
claude mcp add repo-pulse-mcp --env REPO_PULSE_REPOS='<REPO_PULSE_REPOS>' -- npx -y repo-pulse-mcpAdd to claude_desktop_config.json
{
"mcpServers": {
"repo-pulse-mcp": {
"command": "npx",
"args": [
"-y",
"repo-pulse-mcp"
],
"env": {
"REPO_PULSE_REPOS": "<REPO_PULSE_REPOS>"
}
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"repo-pulse-mcp": {
"command": "npx",
"args": [
"-y",
"repo-pulse-mcp"
],
"env": {
"REPO_PULSE_REPOS": "<REPO_PULSE_REPOS>"
}
}
}
}Add to .vscode/mcp.json
{
"servers": {
"repo-pulse-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"repo-pulse-mcp"
],
"env": {
"REPO_PULSE_REPOS": "<REPO_PULSE_REPOS>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"repo-pulse-mcp": {
"command": "npx",
"args": [
"-y",
"repo-pulse-mcp"
],
"env": {
"REPO_PULSE_REPOS": "<REPO_PULSE_REPOS>"
}
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"repo-pulse-mcp": {
"command": "npx",
"args": [
"-y",
"repo-pulse-mcp"
],
"env": {
"REPO_PULSE_REPOS": "<REPO_PULSE_REPOS>"
}
}
}
}Using several servers? Build one config file with the MCP config generator.
Configuration
REPO_PULSE_REPOSAbsolute paths of the git repositories to serve, separated by ':' (';' on Windows)RequiredREPO_PULSE_TOOLSComma-separated toolsets (review, ownership, releases, history) or tool names to enable; all tools by default
Tools this server provides (13)
Taken from the project documentation; the running server may differ.
- review_context
- Briefing for a branch or PR with risky files, left-out files and reviewers.
- file_hotspots
- Files ranked by change frequency and bug fixes.
- change_coupling
- File pairs that change in the same commits.
- knowledge_map
- Who knows a file or directory, bus factor and single-owner files.
- code_age
- How long ago files last changed and oldest directories.
- contributor_summary
- Commits per author in a time window.
- release_notes_draft
- Commits between two refs grouped by type, with Markdown.
- list_tags
- Tags newest first with unreleased count.
- compare_refs
- Ahead/behind counts and commits between two refs.
- stale_branches
- Branches with no recent commits and whether merged.
- recent_activity
- Commits from the last N days.
- commit_search
- Commits whose message matches text.
- file_history
- A file's commits with line stats across renames.
What it does
- Branch review briefing
- Ranks changed files by churn and fixes, spots files left out of the change and suggests reviewers.
- Bug hotspots
- Shows which files change most often and how many of those changes were fixes.
- Change coupling
- Finds file pairs that keep changing in the same commits, revealing hidden dependencies.
- Ownership and bus factor
- Weights recent work to show who knows a file or directory and which files depend on one person.
- Release notes drafting
- Groups commits between two refs by conventional-commit type and outputs Markdown.
- Built-in prompts
- Includes review_branch, release_notes, ownership_report, cleanup_branches and more.
Good for
- Check a branch for risky files and forgotten tests before opening a pull request
- Find the files that keep breaking to plan refactoring
- Identify single-person knowledge risk in a module
- Draft release notes since the last tag
- List stale or already-merged branches to clean up
Pricing
Open source
repo-pulse FAQ
Does it change my repository?
No. It is read-only and all tools are annotated readOnlyHint true.
Does it need network access or a GitHub token?
No. It reads local git data only and never uses the network.
What are the requirements?
Node.js 22.12 or newer and git.
Can I limit which tools are exposed?
Yes. Set REPO_PULSE_TOOLS to a list of toolsets (review, ownership, releases, history) or tool names.
Is repo-pulse free?
Yes. repo-pulse is open source, so you can use and self-host it for free.
How do I add repo-pulse to Claude Code?
Run this command in your terminal: claude mcp add repo-pulse-mcp --env REPO_PULSE_REPOS='<REPO_PULSE_REPOS>' -- npx -y repo-pulse-mcp
What are the best alternatives to repo-pulse?
The closest alternatives to repo-pulse are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.
Where this comes from
- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.


