{
  "markdown": "# koncepto\n\n> Semantic concept graph MCP server for codebases — what your code **means**, not just what it does.\n\n[![Status](https://img.shields.io/badge/status-pre--alpha-orange)]() [![License](https://img.shields.io/badge/license-MIT-blue)]() [![pnpm](https://img.shields.io/badge/pnpm-workspace-yellow)]() [![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/yourtechtribe-labs/koncept-mcp/badge)](https://scorecard.dev/viewer/?uri=github.com/yourtechtribe-labs/koncept-mcp)\n\n## What\n\nCode 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:\n\n- \"Fix B\" lives in 7 files but isn't a function or a class\n- \"All UI counting workload must exclude manual-override participants\"\n- \"Sector value strings must match `SectorAssignment.sector` keys exactly\"\n\n`koncepto` is the curated semantic layer. Concepts in YAML, queryable via MCP tools, read at Step 0 before editing.\n\n## Status\n\n**Pre-alpha** (`v0.1.0-alpha.3` on npm). Schema and tool surface may break before `0.1.0` final. See [roadmap](./ROADMAP.md).\n\nDogfooded against this repo itself: 5 concepts in [.koncept/concepts/](./.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.\n\n## Quickstart\n\n```bash\n# Install in your project\npnpm add -D @yourtechtribe-labs/koncept-cli@alpha\n\n# Bootstrap\nnpx koncepto init\n\n# Write a concept (YAML)\n$EDITOR .koncept/concepts/my-concept.yaml\n\n# Verify\nnpx koncepto verify\n\n# Register MCP server (Claude Code)\nclaude mcp add --scope user koncepto -- \\\n  npx -y @yourtechtribe-labs/koncept-mcp-server@alpha \"$PWD\"\n```\n\n## Enforced invariants\n\nAn invariant is **advisory** by default — surfaced to agents via `koncept_for_file`,\nbut never evaluated. Give it a `check` and it becomes an **enforced gate** that\n`koncepto verify` fails on:\n\n```yaml\ninvariants:\n  - id: invalidate-projection-cache\n    description: A standalone sync that invalidates the banking cache must also\n      invalidate the projection cache, or the /cashflow opening balance goes stale.\n    severity: high\n    check:\n      kind: implication        # per participant file: if it matches `if`, it must also match `then`\n      over: { role: writer }\n      if: \"BankingCacheService\"\n      then: \"CacheInvalidationService|on_full_sync\"\n```\n\nStatic kinds (`implication`, `symbol_present`, `forbidden`, `grep`) run on\n`koncepto verify` by default (fast, read-only; `--no-checks` to skip). The shell\nescape hatch (`kind: command`) runs only on `koncepto check`. This turns a\n\"completion-contract\" concept into both the checklist **and** its enforcement gate —\nthe loose end can't be skipped under momentum.\n\n## Architecture\n\n3 packages under pnpm workspace:\n\n- `@yourtechtribe-labs/koncept-core` — Zod schema, YAML parser, indexer\n- `@yourtechtribe-labs/koncept-mcp-server` — MCP stdio server (4 tools)\n- `@yourtechtribe-labs/koncept-cli` — `init`, `verify`, `list`, `link`\n\n## License\n\nMIT — see [LICENSE](./LICENSE).\n",
  "bytes": 3188,
  "sha": "cf325eb03a75dad5c400195bcb552c865d6a13bb4b6161ffaf26d233724860fd",
  "repo_slug": "yourtechtribe-labs/koncept-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_yourtechtribe_labs_koncept_mcp_75138e48/readme"
}