
Git Archaeologist
io.github.engrmazizPublished by GitHub account engrmazizv0.1.1Updated Oct 24, 2026
Trace code history, commit reasoning, and PR context directly from Git logs.
Overview
Lets an assistant trace code history, commit reasoning, and pull request context from a local Git repository's logs.
- What you can do
- Git Archaeologist is a local MCP server that gives an assistant access to a repository's Git history. According to its registry description, it traces code history, commit reasoning, and pull request context directly from Git logs. No individual tools are listed in the manifest, so the exact operations it exposes are not documented here.
- When to use it
- Consider it when you want an assistant to answer questions about why code changed, who changed it, or how a change relates to a pull request, using the repository's own commit history. It is a desktop-only local process, so it suits developers working in a checkout on their own machine rather than a hosted or browser-based setup.
- Requirements
- Runs as a local process over stdio, installed from the npm package git-archaeologist-mcp, so a Node.js runtime is needed. The manifest declares no authentication, environment variables, or headers. It is desktop-only and not web-executable, and it needs access to a local Git repository to read history from.
Installation
In SourceWeft
- Open Git Archaeologist in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.