growmos — MCP server for Claude Code: a repo knowledge graph
Keeps one shared memory of your repository for you and your agents: answers questions with edge citations, records facts, and fact-checks claims.
claude mcp add growmos -- uvx growmosWhat growmos does
growmos builds a knowledge graph out of what you already write: docs, ADRs, READMEs, design notes, session logs. Entities become nodes, short verb-phrase relations become edges, and each edge carries its provenance. Content is hashed, so only what changed re-enters the pipeline.
Writes are one-liners — growmos remember, link, journal. New names get matched against the canonical set; anything unmatched turns into a provisional cluster instead of disappearing. growmos query serializes the k-hop subgraph around a question and the answer has to cite edge ids, while growmos check verifies claims against edges.
No API key is required for the normal path: the CLI handles the deterministic work and hands extraction, resolution and summarization to whichever agent you run, as a task packet with a prompt, a JSON shape and the exact growmos apply command. Python ≥ 3.9 is the only prerequisite. Headless mode (growmos ingest) covers cron and CI, and that path does call an API.
What it helps with
- turn READMEs and ADRs into a queryable graph
- answer a multi-hop question about the code with edge citations
- record a fact from a session and link it to existing nodes
- fact-check an agent's claim against its sources
- keep the graph current after a commit without running anything by hand
Example prompts for the agent
- Run growmos init in this repo and show me the first task packet
- Take the extraction packet from growmos next and process README.md
- What does the graph say about the Store and who decided that?
How to install growmos
Platform CLI
claude mcp add growmos -- uvx growmosuvx runs the command named after the package; if the README names another one, use uvx --from growmos <command>
Platform CLI
codex mcp add growmos -- uvx growmosuvx runs the command named after the package; if the README names another one, use uvx --from growmos <command>
Config file
{
"mcpServers": {
"growmos": {
"command": "uvx",
"args": [
"growmos"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from growmos <command>
Config file
{
"servers": {
"growmos": {
"type": "stdio",
"command": "uvx",
"args": [
"growmos"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from growmos <command>
Platform CLI
gemini mcp add growmos uvx growmosuvx runs the command named after the package; if the README names another one, use uvx --from growmos <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about growmos
How do I install growmos in Claude Code?
Run claude mcp add growmos -- uvx growmos. The server starts through uvx, so there is nothing to install separately.
What does growmos do?
It maintains a living knowledge graph of your repository: grounded answers with edge citations, remembered and linked facts, and claim checking. It runs as an MCP server on top of the CLI.
Does growmos need an API key?
Not for regular use — the CLI does the deterministic part and your agent does the judgment work. A key is only needed for headless growmos ingest in cron or CI.
