MCP server for Claude Code
Loom app icon

Claude Code
never forgets

Loom gives Claude Code persistent memory across sessions. Log decisions, archive context intelligently, search patterns across every project.

$npm install -g @pixelguild/loom

How it works

Seamless across sessions

Loom runs as an MCP server. Claude uses it automatically — no commands to remember, no workflow changes.

01

Session starts

Claude reads your context file and picks up exactly where you left off. Full project history in seconds.

02

Claude works

As Claude makes decisions, solves problems, and hits dead ends, Loom logs everything automatically.

03

Context grows

When context gets large, Loom spawns a Claude subprocess to produce an intelligent narrative archive.

04

Next session

The carry-forward summary + current context gives Claude complete project history. No old archives needed.

Features

Everything your sessions need.
Nothing they don't.

Nine MCP tools that Claude uses automatically. No commands to learn, no workflow changes.

Context logging

Structured entries for decisions, actions, issues, questions, and dead ends. Every session builds on the last.

Intelligent archiving

When context grows large, a Claude subprocess produces narrative archives with rolling carry-forward summaries. History stays bounded.

Cross-project patterns

Save reusable solutions to a global SQLite library with full-text search. What you solve once is findable everywhere.

Peer LLM consultation

Ask OpenAI, Vertex AI, or Ollama for a second opinion on architecture, debugging, or design decisions.

Execution manifests

Save structured plans as markdown files. Each includes a generated launch command for headless claude runs.

Per-project config

Layered configuration. Global defaults in ~/.loom/config.json, per-project overrides in docs/loom/loom.config.json.

MCP Tools

9 tools. Zero config.

Claude discovers and uses these tools automatically via the Model Context Protocol.

ToolAuto
loom_get_context

Read current session context at startup

loom_log_context

Log decisions, actions, issues, questions, dead ends

loom_get_session_status

Token count, archive count, threshold status

loom_archive_context

Intelligent narrative archive with carry-forward summary

loom_save_pattern

Save reusable patterns to the global library

loom_find_pattern

Full-text search across all projects' patterns

loom_create_manifest

Save structured execution plans for headless runs

loom_get_manifest

List or retrieve saved execution manifests

loom_consult_peer

Ask OpenAI, Vertex AI, or Ollama for a second opinion

Auto = Claude uses these without being asked

Get started

One command. Done.

Run the init command in any project. Loom handles the rest.

1

Install globally

$ npm install -g @pixelguild/loom
2

Initialize your project

$ loom init

Creates docs/loom/, wires MCP into .claude/mcp.json, and adds instructions to your CLAUDE.md.

3

Start a Claude Code session

Claude automatically reads existing context, logs progress as it works, archives when context gets large, and resumes seamlessly next session.

4

Check status anytime

$ loom status

Shows token count, archive count, last entry, and whether archiving is needed.

Or add manually to any project:

$ claude mcp add loom -- loom
Loom
Native macOS companion app

Browse your context
without a terminal

A native SwiftUI menubar app for browsing project context, archives, and patterns at a glance. Read-only, fast, always accessible.

Download for macOS
macOS 14+Apple Silicon + IntelFree