Graphkeeper MCP server
Mines git history for file co-change patterns into a queryable knowledge graph via MCP.
0 stars
Reviews
Write oneNobody has reviewed Graphkeeper yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Graphkeeper tools (1, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
runwrite actionRun the graphkeeper CLI with `args` (subcommand + its own arguments, e.g. ["build", "."] or ["query", "co-change", "src/index.ts"]) and return its parsed `--json` output. `--json` is appended automatically, callers should not pass it themselves.
Public scan report
scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it
- Code scan11 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 11 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
What the publisher says
From the Graphkeeper repository's README, as published. We do not edit it. Read it on GitHub
GraphKeeper
<!-- mcp-name: io.github.RudrenduPaul/graphkeeper --> <!-- Ownership-proof string for registry.modelcontextprotocol.io publishing. Do not remove. -->
Install • Quickstart • CLI Reference • Comparison • FAQ
A local-only CLI that mines your git log for which files actually change together, then hands an AI coding agent a queryable answer instead of a grep across the whole history.
npx graphkeeper-cli build
npx graphkeeper-cli query co-change src/git.tsFiles that historically change alongside "src/git.ts":
1 src/store.ts
1 src/types.ts
1 test/git.test.ts
1 test/store.test.ts
1 test/test-helpers.ts(Real output from running GraphKeeper against its own repo, this early in its history. Co-change counts grow as a codebase accumulates more commits.)
No server, no account, no embeddings API. Every byte of output comes from git log on the repo you already have checked out.
Install
GraphKeeper ships two independent, equally first-class packages. Pick whichever fits your toolchain, or install both. Both mine the same git log co-change signal and share one on-disk .graphkeeper/graph.json schema, so a store built by either can be read back by the other.
# npm -- JavaScript/TypeScript CLI + library
npm install -g graphkeeper-cli
# or run it once with no install
npx graphkeeper-cli build
# PyPI -- Python CLI + library (genuine port, not a wrapper around the Node binary)
pip install graphkeeper-cliThe npm package requires Node.js 18 or later; the Python package requires Python 3.9 or later. Both require git on your PATH. The Python package's CLI entry point is also graphkeeper (e.g. graphkeeper build). See python/README.md for the Python-specific walkthrough, and CHANGELOG.md for each distribution's version history.
Quickstart
Run it against any git repo, including this one:
git clone https://github.com/RudrenduPaul/GraphKeeper.git
cd GraphKeeper
graphkeeper buildGraphKeeper build complete: /path/to/GraphKeeper
Co-change graph: 4 commit(s) analyzed, 80 file pair(s) found
graphify enrichment: skipped -- graphify was not found on PATH. Install it with
`uv tool install graphifyy` (or `pipx install graphifyy`) for symbol/call-graph
enrichment; GraphKeeper works fine without it, in co-change-only mode.
Wrote /path/to/GraphKeeper/.graphkeeper/graph.jsonNow query it:
graphkeeper query co-change src/git.tsFiles that historically change alongside "src/git.ts":
1 src/store.ts
1 src/types.ts
1 test/git.test.ts
1 test/store.test.ts
1 test/test-helpers.tsIf graphify is installed (uv tool install graphifyy), graphkeeper build automatically shells out to its local, no-API-key graphify extract --code-only and merges its symbol/call-graph into the same store, unlocking call-graph queries:
graphkeeper query calls mineCoChangemineCoChange() (src/git.ts)
Calls (2):
--> assertIsGitRepo()
--> runGit()
Called by (1):
<-- build()(Also real output, from running graphkeeper build against this repo with graphify installed.)
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Install directly
claude mcp add graphkeeper -- uvx graphkeeper-cli
Graphkeeper: common questions
- Is Graphkeeper MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Graphkeeper safety report
- How do I install Graphkeeper?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Graphkeeper need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Graphkeeper maintained?
- The last commit was 11 days ago (2026-09-13). The latest release is v0.1.5.
- What can I use instead of Graphkeeper?
- Servers from other publishers that do the same job: argot MCP server, Kindex MCP server and Kindex MCP server. Compare all Graphkeeper alternatives.
Alternatives to Graphkeeper
Same job from other publishers: the closest match first, then the best rated.
- argotRead-only context and complete checks against patterns learned from git history. Local; no LLM.not reviewedGrowingB
- KindexPersistent knowledge graph and MCP server for AI workflows with git-tracked project context.not reviewedGrowingA
- KindexPersistent knowledge graph and MCP server for AI workflows with git-tracked project context.not reviewedGrowingB
- SrclightDeep code indexing for AI agents. FTS5 + embeddings + call graphs + git intelligence. Fully local.not reviewedEstablishedA
Obsidian EverywhereGraph context, semantic search, guarded edits, and reviewable Git for local Obsidian vaults.not reviewedGrowingA