
moe1177/cairn
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
A map of all your repos for coding agents: one index, one card per repo, an MCP server. Works with Claude Code, Codex, Gemini CLI and Cursor.
概要
cairn scans every git repo in a folder once, works out how they connect, and gives your agent: - a tiny always-loaded index; - a short card per repo. The agent knows where things live without re-exploring. Cairns are the stacked-stone markers that guide hikers along a trail. cairn leaves small, cheap markers that guide coding agents to the right repo, and then to the right file. Works with , on . Using Claude Code? Install cairn as a plugin, or paste that section into Claude Code and it installs everything for you. Coding agents work inside one repo. Real work spans many: a web app, an API, a shared types package, a payments service, a reporting job. Say "add a tip amount to trips end to end" and the agent has to: 1. discover that sibling repos exist; 2. grep through all of them; 3. read a pile of files; 4. guess which service owns the trips table. That costs tokens and turns, and weaker models guess wrong. Hand-maintained "related repos" docs help until they go stale.
README
以下は原文 README の抜粋です。原文を見る。
cairn
A map of all your repos for coding agents. cairn scans every git repo in a folder once, works out how they connect, and gives your agent:
- a tiny always-loaded index;
- a short card per repo.
The agent knows where things live without re-exploring.
Cairns are the stacked-stone markers that guide hikers along a trail. cairn leaves small, cheap markers that guide coding agents to the right repo, and then to the right file.
Works with Claude Code, Codex, Gemini CLI, and Cursor, on Windows, macOS, and Linux. Using Claude Code? Install cairn as a plugin, or paste that section into Claude Code and it installs everything for you.
Why
Coding agents work inside one repo. Real work spans many: a web app, an API, a shared types package, a payments service, a reporting job. Say “add a tip amount to trips end to end” and the agent has to:
- discover that sibling repos exist;
- grep through all of them;
- read a pile of files;
- guess which service owns the
tripstable.
That costs tokens and turns, and weaker models guess wrong.
Hand-maintained “related repos” docs help until they go stale. cairn builds that map from the code itself and keeps it fresh:
~/code/ ~/code/.cairn/
├── rider-web/ cairn ├── INDEX.md ← ~25 tokens per repo, always loaded
├── trips-svc/ ─────▶ ├── cards/trips-svc.md ← read on demand (≤ 800 tokens)
├── payments-svc/ scan ├── workspace.json ← the full graph
├── analytics-etl/ └── authored/ ← your summaries and decisions
└── …
What your agent sees
The index is a few lines, loaded into every session through CLAUDE.md or an equivalent:
# Workspace repos (cairn)
- admin-console (@fleetline/admin-console): Next.js back-office for ops staff; queries trips… · nextjs
- analytics-etl: Nightly SQL reporting jobs over trips, payments, drivers… · python
- payments-svc (payments): Go service that charges completed trips and records weekly payouts · go
- trips-svc: FastAPI service owning the trip lifecycle and the trips/trip_events tables · fastapi · used by admin-console
- ui-kit (@fleetline/ui-kit): Shared React components (Button, Card) · react · used by admin-console
インストール
This server does not publish a one-line install command.
Open the repository installation guide MCP 初心者?mcpskill.org のガイドから始めましょう →