The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Koncept MCP Server listing page.
Semantic concept graph MCP server for codebases — what your code means, not just what it does.
Code graphs (Aider repomap, GitNexus, Sourcegraph) capture structural relations: who imports who, who calls who. They miss semantic invariants — the cross-cutting concepts that live in code not related by imports:
SectorAssignment.sector keys exactly"koncepto is the curated semantic layer. Concepts in YAML, queryable via MCP tools, read at Step 0 before editing.
Pre-alpha (v0.1.0-alpha.3 on npm). Schema and tool surface may break before 0.1.0 final. See roadmap.
Dogfooded against this repo itself: 5 concepts in .koncept/concepts/ cover the schema, the registry, the MCP tool contract, the monorepo shape, and the kebab-id naming convention. pnpm dogfood = koncepto verify against its own registry.
An invariant is advisory by default — surfaced to agents via koncept_for_file,
but never evaluated. Give it a check and it becomes an enforced gate that
koncepto verify fails on:
Static kinds (implication, symbol_present, forbidden, grep) run on
koncepto verify by default (fast, read-only; --no-checks to skip). The shell
escape hatch (kind: command) runs only on koncepto check. This turns a
"completion-contract" concept into both the checklist and its enforcement gate —
the loose end can't be skipped under momentum.
3 packages under pnpm workspace:
@yourtechtribe-labs/koncept-core — Zod schema, YAML parser, indexer@yourtechtribe-labs/koncept-mcp-server — MCP stdio server (4 tools)@yourtechtribe-labs/koncept-cli — init, verify, list, linkMIT — see LICENSE.