Read-only MCP server for commit-pinned, cited context across local Git repositories.
claude mcp add repocontext -- npx -y @shmindmaster/gitpin{
"mcpServers": {
"repocontext": {
"command": "npx",
"args": ["-y", "@shmindmaster/gitpin"]
}
}
}MCP Servers overview
# GitPin
[](https://github.com/shmindmaster/repocontext/actions/workflows/ci.yml)
[](LICENSE)
[](package.json)
[](https://modelcontextprotocol.io)
[](https://www.npmjs.com/package/@shmindmaster/gitpin)
### Pin agent answers to Git HEAD. Path. Line. Full SHA. Prove. Verify.
**GitPin is not another “repo context” MCP.** That category is full of vector indexes, dump files, and remote GitHub browsers. GitPin is a **trust product**: index-free, read-only, multi-repo **evidence** agents must prove and humans can re-check with `git show`.
```text
Agent claim
→ pin.search_* (candidates only)
→ pin.prove (evidence pack: path + line + full SHA + content hash)
→ pin.verify (git show re-check; HEAD match report)
→ you run: git show <sha>:<path>
```
| Crowded category | GitPin product |
| --- | --- |
| Vector / SQLite “repo context” servers | **No embeddings, no DB, no reindex** |
| Filesystem MCP (writes) | **Never writes indexed repos** |
| One-shot repo dumps | **Live prove → verify MCP loop** |
| Grep hits as “the answer” | **Candidates → evidence pack → verification report** |
| GitHub platform MCP | **Local Git roots (private/offline)** |
Formerly `@shmindmaster/repocontext` (0.3.x). See [migration](docs/migration-gitpin.md).
> **Release:** `@shmindmaster/gitpin@0.4.0`. Install: `npx -y @shmindmaster/gitpin@latest`. Node 20+.
## Five-minute path
```bash
# From a committed Git repository
npx -y @shmindmaster/gitpin@latest init --client codex
```
`init` creates `~/.gitpin/repositories.yaml` **outside** the repo, runs `doctor`, prints a **first evidence line with full SHA**, and paste-ready MCP config. It never edits the indexed repository.
```bash
# Independently verify any claim (same contract as pin.verify)
npx -y @shmindmaster/gitpin@latest verify \
--repository my-service \
--path docs/architecture.md \
--line 42 \
--sha <full-or-short-hex>
```
## Product job
**When** agents invent file contents, mix dirty worktrees, or cite the wrong branch
**You want** every fact re-checkable with `git show <sha>:<path>`
**GitPin** registers local Git roots, serves **HEAD-only** docs/code, flags **stale** tracked docs, returns **path / line / SHA**, and closes the loop with **`pin.verify`**.
### Agent tool surface (`pin.*`) — 12 read-only tools
| Job | Tools |
| --- | --- |
| Discover | `pin.catalog` |
| Find candidates | `pin.search_docs`, `pin.search_code` |
| Prove | `pin.prove` (primary), `pin.prove_set` (1–8 cites), `pin.get_doc`, `pin.read` |
| Verify | `pin.verify`, `pin.verify_set` |
| Decide | `pin.analyze` → `EvidenceBrief` |
| Inspect / diff | `pin.inspect`, `pin.compare` |
Resource: `gitpin://catalog`. Prompt: `prove-with-git-head` (forces the product loop).
Cite formats: [docs/cite-spec.md](docs/cite-spec.md). Agent skill template: [templates/gitpin-skill.md](templates/gitpin-skill.md).
### Functionality that is the pivot (not a rename)
- **Evidence pack** (`pin.prove`): claim binding, line slice, full SHA, `contentSha256`, `citation.cite` / `handle`, next-step verify.
- **Multi-cite sets** (`pin.prove_set` / `pin.verify_set`): stable `evidenceSetId` for multi-repo answers and CI.
- **Verification report** (`pin.verify` / CLI): independent `git show`; optional `mustContain` claim-text; status includes `contradicted`.
- **Candidates, not claims**: search returns `kind: evidence-candidates` with forced `next: pin.prove`.
- **EvidenceBrief**: multi-repo knownFacts / gaps / stable `evidenceSetId` (schema v2).
- **Dirty exclusion**: uncommitted work is never cited as HEAD evidence.
### Explicit non-goals
- Semantic / embedding search
- Writing, committing, or pushing
- Replacing GitHub Issues/PRs automation
- Indexing non-Git umbrella folders as one “repo”
## Configuration
| Variable | Purpose |
| --- | --- |
| `GITPIN_REGISTRY` | Registry YAML path (alias: `REPOCONTEXT_REGISTRY`) |
| `GITPIN_MCP_TOKEN` | HTTP bearer token (alias: `REPOCONTEXT_MCP_TOKEN`) |
| `GITPIN_ALLOWED_HOSTS` | HTTP host allowlist (alias: `REPOCONTEXT_ALLOWED_HOSTS`) |
Default registry: `~/.gitpin/repositories.yaml` (falls back to `~/.repocontext/...` if present).
## Docs
[Tools](docs/tools.md) · [Compare](docs/compare.md) · [FAQ](docs/faq.md) · [Migration](docs/migration-gitpin.md) · [Clients](docs/clients.md) · [Architecture](docs/architecture.md) · [Competitive landscape](docs/research/competitive-landscape-corrected-2026-07-30.md)
Site: [shmindmaster.github.io/repocontext](https://shmindmaster.github.io/repocontext/) (GitHub path may stay `repocontext`; product name is **GitPin**).
## Development
```bash
corepack enable
pnpm install --frozen-lockfile
pnpm validate
pnpm build
pnpm verify:package
pnpm site:test
```
## License
[MIT](LICENSE)
What people ask about repocontext
What is shmindmaster/repocontext?
+
shmindmaster/repocontext is mcp servers for the Claude AI ecosystem. Read-only MCP server for commit-pinned, cited context across local Git repositories. It has 0 GitHub stars and was last updated today.
How do I install repocontext?
+
You can install repocontext by cloning the repository (https://github.com/shmindmaster/repocontext) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.
Is shmindmaster/repocontext safe to use?
+
shmindmaster/repocontext has not been audited yet by our security agent. Review the original repository on GitHub before using it in production.
Who maintains shmindmaster/repocontext?
+
shmindmaster/repocontext is maintained by shmindmaster. The last recorded GitHub activity is from today, with 3 open issues.
Are there alternatives to repocontext?
+
Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.
Deploy repocontext to your cloud
Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.
Maintain this repo? Add a badge to your README
Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.
[](https://claudewave.com/repo/shmindmaster-repocontext)<a href="https://claudewave.com/repo/shmindmaster-repocontext"><img src="https://claudewave.com/api/badge/shmindmaster-repocontext" alt="Featured on ClaudeWave: shmindmaster/repocontext" width="320" height="64" /></a>More MCP Servers
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
An open-source AI agent that brings the power of Gemini directly into your terminal.
The fastest path to AI-powered full stack observability, even for lean teams.
Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl!