MCP · Claude Code · local-first

Claude can remember your codebase now.

xtage gives Claude persistent, semantic knowledge of your codebase — across every session, without manual context-setting.

Get started npm package

Install claude mcp add xtage npx -- -y @ruco-ai/xtage

The problem

Claude starts cold every session.

Every new conversation, you re-explain the architecture, the conventions, the decisions that were made. xtage fixes this by maintaining a knowledge base that Claude reads automatically before touching any source files.

How it works

Three tiers, one command.

Run xtage init once. Claude builds a structured knowledge base of your repo and loads it silently at the start of every future session.

Structural map

REPO.md, CODEINDEX.md, PROJECTINSIGHTS.md — architecture, file roles, design decisions.

File summaries

Per-file prose summaries in files/{slug}.md — loaded instead of opening source.

Source files

Opened only when the above tiers are insufficient. Usually they aren't.

CLI

Five commands. That's it.

xtage init Index your repo — local filesystem by default, or pass a GitHub URL

xtage start Load codebase context at the start of a session

xtage end Persist session learnings to PROJECTINSIGHTS.md

xtage update Incrementally refresh the index after commits

xtage status Check index freshness

Design principles

Local. Private. Yours.

◈

Local-first

All data lives in ~/xtage/ on your machine. No cloud, no sync.

◈

No external AI

Indexing runs through your own Claude. No third-party API calls.

◈

Works offline

Local indexing needs no network. Private repos, air-gapped environments — all fine.

◈

MCP-native

Integrates with Claude Code, Claude Desktop, Cursor, and any MCP-compatible client.