Mache 프로젝트는 navigable 그래프로 데이터를 구조화했습니다. 모든 구조 소스에서 설명 된 스키마를 포인트 - JSON 문서, SQLite 데이터베이스, 소스 코드 - 그리고 mache는 MCP 도구 또는 마운트 파일 시스템로서의 투영을 노출, 그래서 에이전트 (또는 당신)는 평평한 파일 대신 topology를 탐구 할 수 있습니다.

1개의 엔진, 많은 투상. examples/] 프로젝트 CVE 피드 (NVD, KEV), Notion 수출, Trivy 검사 결과, Terraform, Markdown, LLM 대화 로그 및 프로젝트 Go 또는 Rust 소스 같은 기계와 감사 흔적. **Code 지능은 그 엔진의 주력 응용 프로그램입니다 ** - 그래프가 기능, 유형, 상호 참조, 통화 체인, 구조적 인 냄새 규칙 및 옵션 LSP 등급의 풍부를 얻는 가장 개발 된 투사.

Mache (/mme/ mah-shay): papier-mâché — 원료에서, 분쇄하고 모양으로 remolded.

빠른 시작

그것은 주력 응용을위한 30 초 경로입니다 - ** 코드베이스에 코드 지능.

Mache

Mache projects structured data into a navigable graph. Point a declarative schema at any structured source — JSON documents, SQLite databases, source code — and mache exposes the projection as MCP tools or a mounted filesystem, so an agent (or you) can explore the topology instead of grepping flat files.

One engine, many projections. The schemas in examples/ project CVE feeds (NVD, KEV), Notion exports, Trivy scan results, Terraform, Markdown, LLM conversation logs, and audit trails with the same machinery that projects Go or Rust source. Code intelligence is the flagship application of that engine — the most-developed projection, where the graph gains functions, types, cross-references, call chains, structural smell rules, and optional LSP-grade enrichment.

Mache (/mɑʃe/ mah-shay): from papier-mâché — raw material, crushed and remolded into shape.

Quick start

git clone https://github.com/agentic-research/mache.git
cd mache && task build && task install
mache init --global   # installs the keepalive HTTP daemon (:7532) + registers detected editors

That’s the 30-second path for the flagship application — code intelligence on a Go codebase. mache init --global installs a per-user supervisor (launchd on macOS, systemd --user on Linux) that keeps the shared mache HTTP daemon alive on localhost:7532 and registers it with Claude Code and any detected editors — no terminal to babysit. Then mache init (no flag) inside a project records what that project serves.

Two things new users hit:

• HTTP is the canonical transport. One shared daemon serves every project, routing per session via the MCP roots protocol. --stdio exists only as an escape hatch for CI / sandboxes / headless agents and is never registered for editor use (see ADR-0022).
• ley-line-open is a hard requirement, not an add-on. Since v0.18.0 mache has no in-process parser: leyline parse produces the _ast database that every source projection reads. task install provisions the pinned binary from a checkout; mache install does the same from a release asset or package-manager install, where there is no Taskfile. Point mache at a directory or a pre-built .db — both route through leyline; a pre-built .db just skips the parse step and can carry LSP/embedding enrichment.

To project non-code data instead, hand mache serve (or the root mount form, mache ) a schema with --schema and point it at your JSON or SQLite source — the example schemas cover NVD, KEV, Notion, Trivy, Terraform, and more.