open-company-brain GitHub Details, Stars and Alternatives | OpenRepoFinder
PDgit12 / repository
open-company-brain
The open-source company brain that powers a closed loop — model-free, over MCP. Ingest your docs; your AI tool (Claude, Cursor, Copilot) answers with citations or refuses. Record how-work-gets-done as skills, govern real actions with human approval + audit, and let the loop learn from outcomes. Bring your own model, data, and infra.
A transparent discovery signal based on current public GitHub metadata.
Recent activity35% weight
90
Community adoption25% weight
0
Maintenance state20% weight
100
License clarity10% weight
100
Project information10% weight
100
This score does not audit code, security, maintainers, documentation quality, or suitability. Verify the repository and its current documentation before adoption.
README preview
Comb
The model-free company brain your AI plugs into over MCP.
Give your AI tool (Claude, Cursor, Copilot) one governed, cited, scope-safe memory of
what your company knows — so it answers from your real docs or refuses, never invents.
Comb runs no model of its own: your AI brings the intelligence, Comb owns the data,
the access rules, the refusal, and the audit trail.
The problem
A company's knowledge is scattered across docs, PDFs, Word files, Slack, and people's heads.
Ask an AI "what's our refund policy?" and it guesses, or you paste the doc in every time — and
every teammate's AI gives a different answer. There is no single, current, trusted source the
AI can pull from, and nothing stops it from making an answer up.
Comb is that source. Scope-gated (Team A can't read Team B), kept current, and it refuses
when it doesn't know instead of hallucinating.
Why Comb
Most tools in this space are either enterprise search you can't self-host or a thin RAG wrapper
that still makes things up. Comb is different on three axes that matter for real work:
Governed, not just retrieved. Access scopes are enforced on every read, every action is
human-approved and audited, and answers are cited or refused — never invented.
Model-free and self-hosted. Comb runs no model of its own; your AI tool brings the
intelligence over MCP. The default is keyword retrieval over a single file — $0/query, no database.
It compounds. Every recorded outcome re-ranks what the brain trusts, so answers get better
with use instead of going stale.
ALGORITHMICALLY RELATED
Similar Open-Source Projects
Selected from shared topics, language and repository description—not editorial ratings.
Harness as code — the Terraform for AI agents. Define your agent team AND its memory once, deploy to Claude Code, OpenClaw, Cursor, Codex, Gemini, Copilot, Kiro. Declarative .at language + agent-maintained, Obsidian-portable company brains + interactive visualizer.
The Open-Source Career Operating System. 146+ AI Agents, Resume Intelligence, Interview Intelligence, Job Search Intelligence, Career Paths, Company Tracks, ATS Resume Studio, Career CLI, and Career Knowledge Graph.
Comb is built for engineering and ops teams running AI agents on their own knowledge, where the
answers need to be right and accountable, not just fluent. If you only want to ask a single file a
question, your AI tool already does that — Comb earns its place when many people and agents need
the same trusted, current knowledge.
Quickstart — no model, no database, no Docker
npm i -g open-company-brain # installs the `comb` command
comb install claude # wire Comb into Claude / Cursor / VS Code as an MCP server
comb ingest ./company-docs/ # real files: .docx .pdf .md(OKF) .txt .csv .json
Then, in your AI tool (over MCP):
"search the brain — what does the handbook say about refunds?"
Your agent answers from cited records, or refuses. Comb runs no model — retrieval is
keyword-based and your AI host does the thinking. ($0/query, nothing to configure.)
comb ingest ./okf-bundle/ # concept type/title/tags become structured, searchable
comb export --out ./okf-out # write the brain back out as a scope-gated OKF bundle
OKF is the curated layer; Comb adds what OKF files lack — access scopes, cite-or-refuse,
audit, and the learning loop.
A GTM persona over the brain
What a static prompt file can't do: query a corpus past the context window, enforce scopes,
and refuse when ungrounded. Two MCP tools turn the brain into a grounded GTM agent:
gtm_research_prospect { name:"Jane Doe", company:"Acme", role:"CTO" }
→ a dossier built ONLY from cited brain records — or nothing
gtm_draft_outreach { name:"Jane Doe", company:"Acme", angle:"cut their API test maintenance" }
→ a personalized email grounded in cited records; refuses if there's no grounding
Why this is not a RAG wrapper
A RAG wrapper is four steps: ingest → embed → retrieve → hand to an LLM. Comb keeps that
spine and adds the systems work a wrapper skips — all built and tested today:
Concern
RAG wrapper
Comb
Who can read a record
nothing
access scopes asserted on every read
Hallucination control
hope the model cites
deterministic refusal in code before generation
Real-file ingest
usually .txt/.md
.docx · .pdf · OKF · .csv · .json
Doing things
none
propose → approve → execute → audit
Getting better
static
record_outcome → reward → re-ranks retrieval
Proof it works
none
behavioural eval asserted in CI
The model is the easy, swappable part. The governance, refusal, audit, and loop are the product.
Backends
No code change — set LLM_BACKEND. You do not need a vector database; the default is a
single JSON file.
Backend
Recall
Generation
Needs
Cost
modelfree(default)
keyword
your AI host, over MCP
nothing
$0/query
local
pgvector / file-vector
Ollama
Ollama (+ optional Postgres)
$0/query
openai
pgvector / file-vector
any OpenAI-compatible key
your key
your key
langbase
managed
managed
Langbase key
usage
CLI
comb install <client> # wire Comb into Claude/Cursor/VS Code as MCP
comb ingest <file|folder|url> [--source name] [--scope s] [--replace]
comb export [--out dir] [--scope a,b] # write the brain out as an OKF bundle
comb mcp # run the MCP server (stdio)
comb doctor # which backend is live, what's missing
comb reset [--all] [--yes] # clean slate (wipes the real knowledge stores)
comb eval # run the behavioural eval suite
Keeping data fresh (URLs & feeds)
Ingest accepts a URL, and a snapshot is stored — it isn't a live link. To refresh
data that changes over time, re-ingest with --replace: it wipes that source's
old records first, so an updated page/feed replaces its snapshot cleanly instead of
piling stale copies beside it.
For automation, schedule the re-ingest (cron / n8n / Zapier) against the same source,
or POST to the ingest webhook (POST /api/ingest). Comb stores what you give it; it
doesn't poll URLs on its own.
git clone https://github.com/PDgit12/open-company-brain.git
cd open-company-brain && npm install
npm test && npm run typecheck && npm run lint && npm run build