Pasting raw code wastes tokens on boilerplate, imports, and redundant formatting.

LogicStamp Context compiles only what AI needs - deterministic architectural contracts, dependency relationships, and logic signatures - saving up to 65% tokens compared to full source code.

Plus, it provides structured context that AI can actually parse and understand, not just raw text.

Yes. LogicStamp Context is completely free and open-source.

Install it globally with `npm i -g logicstamp-context` and generate AI-ready context bundles immediately.

MCP integration is also available via `logicstamp-mcp` for real-time analysis in Cursor, Claude Desktop, and Claude CLI.

LogicStamp Context currently supports TypeScript codebases including React, Next.js, Express, and NestJS, plus Vue 3 TypeScript/TSX files.

Requires Node.js 20+.

MCP integration is available for Cursor, Claude Desktop, and Claude CLI.

Works with any React/TypeScript styling approach, including Tailwind, CSS modules, SCSS, styled-components, Material UI, ShadCN/UI, Radix UI, and Framer Motion.

Note: Vue Single File Components (`.vue`) are planned for a future release.

Run `npx logicstamp-context context` to get started instantly, or install it globally with `npm i -g logicstamp-context`.

Optionally run `stamp init` in your project directory to set up recommended defaults.

Then run `stamp context` to generate `context.json` bundles plus a `context_main.json` index for AI-ready codebase understanding.

You can validate the output with `stamp context validate`, or use MCP integration for real-time analysis in supported clients.

MCP (Model Context Protocol) provides real-time context analysis directly in Cursor, Claude Desktop, or Claude CLI.

Setup (one-time, global):

1. Install LogicStamp CLI: `npm install -g logicstamp-context`

2. Install MCP server: `npm install -g logicstamp-mcp`

3. Configure your MCP client by adding LogicStamp to your config file:

- Cursor: `~/.cursor/mcp.json` (macOS/Linux) or `%USERPROFILE%\.cursor\mcp.json` (Windows)

- Claude CLI: `~/.claude.json` (macOS/Linux) or `%USERPROFILE%\.claude.json` (Windows)

- Claude Desktop: `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows)

Add this configuration:

{
  "mcpServers": {
    "logicstamp": {
      "command": "npx",
      "args": ["logicstamp-mcp"]
    }
  }
}

LogicStamp Context offers three code inclusion modes: `none` (contracts only, ~79% savings vs full context), `header` (recommended, ~65% savings vs full context, ~70% vs raw source), and `full` (complete source).

The header mode compiles just enough context for AI to understand component logic without wasting tokens on implementation details.

Additionally, you can use `--format toon` for an alternative output format (a compact text-based format) that uses ~40% fewer tokens than JSON while maintaining the same data structure.

Use `stamp context --compare-modes` to see exact savings for your codebase.

Token counts are automatically calculated using model-accurate tokenizers (GPT-4 and Claude) when available, or character-based estimation as a fallback.

LogicStamp Context compiles per-root bundles (one bundle per page/feature component) rather than individual files per component.

Each bundle contains the root component plus its complete dependency graph - all related components together.

This design matches how developers work: when you need help with a specific page or feature, share that bundle and the AI has complete context in one self-contained unit.

The `stamp context style` command compiles context bundles with visual and layout metadata included.

It extracts style information from your components including Tailwind CSS classes, SCSS/CSS modules, inline styles, styled-components/Emotion, framer-motion animations, Material UI, ShadCN/UI, Radix UI, and Styled JSX.

This enables AI assistants to understand visual design, suggest visually consistent components, analyze layout patterns, track color palettes, and identify animations.

Use it when you need AI to understand the visual aspects of your UI (design system analysis, styling questions, visual consistency checks). For logic-only questions, use regular `stamp context` to save tokens. Note: Style metadata adds more tokens (~52-65% of raw source vs ~30% for header mode), so use `--compare-modes` to see the exact cost impact for your codebase.

Yes. Run `stamp context --watch` to automatically regenerate context files when source files change.

It supports incremental rebuilds, change detection, debouncing, and optional style file watching.

For stricter development workflows, `--strict-watch` detects breaking changes and writes violations to `.logicstamp/strict_watch_violations.json` when needed.

Watch mode is designed for development awareness rather than CI enforcement. For CI with exit codes, use `stamp context compare`.

No. LogicStamp is completely read-only.

It analyzes your codebase using the TypeScript AST and generates structured context bundles without modifying any source files.

All output is written to context files that you can share with AI assistants.