Skip to main content

Why Use CodeArchitect MCP?

Saves AI conversations as searchable markdown files. Prevents losing important architectural discussions. Benefits:
  • Preserve knowledge as markdown files
  • Auto-organized by date
  • Searchable with grep/IDE/git
  • Zero configuration

How It Works

MCP Protocol: AI assistants call tools via MCP. CodeArchitect MCP exposes codearchitect_help, store_session, and get_session tools. Storage: Sessions saved to ~/.codearchitect/sessions/YYYY-MM-DD/topic-folder/ in your home directory (always). Each session has summary.md and full.md files. Export File Detection: Automatically detects Cursor/VS Code export files from ~/.codearchitect/exports/. Supports both Cursor (.md) and VS Code (.json) formats. Topic Extraction: Auto-extracts topics from conversation (or use explicit topic parameter). Redundant suffixes like “-summary” are automatically removed. Token Optimization: get_session supports TOON format for ~40% token reduction when sending to LLMs.

Usage

Get Help (Start Here!): Just ask your AI: use codearchitect Store Session (Recommended Workflow):
  1. Export chat from Cursor/VS Code to ~/.codearchitect/exports/
  2. use codearchitect store_session - Auto-detects export file and saves it
  3. Or: use codearchitect store_session topic: "authentication implementation" - Save with topic
  4. Or: use codearchitect store_session exportFilename: "resolve_mcp" - Match specific export file
Get Session:
  • use codearchitect get_session - List all sessions
  • use codearchitect get_session authentication-implementation - Get specific session by folder name
  • use codearchitect get_session 2025-11-18 - List sessions from date
Parameters:
  • codearchitect_help: feature (optional) - Get help for all features or specific feature
  • store_session: conversation (optional - auto-detects export file), exportFilename (optional), topic (optional), format (“plain” or “messages”), projectDir (optional)
  • get_session: filename (optional), date (optional), format (“json”, “toon”, or “auto”), limit (optional)

Where Are Sessions Stored?

Main location (always): ~/.codearchitect/sessions/YYYY-MM-DD/topic-folder/
  • Windows: C:\Users\YourName\.codearchitect\sessions\
  • Linux/Mac: ~/.codearchitect/sessions/
Structure:
~/.codearchitect/sessions/
└── YYYY-MM-DD/
    └── topic-folder-name/
        ├── summary.md    # Quick summary + key points
        └── full.md       # Complete conversation
Export folder: ~/.codearchitect/exports/
  • Export chats here for automatic detection
  • Supports both Cursor (.md) and VS Code (.json) formats
Optional project location: project/.codearchitect/sessions/
  • Only if projectDir parameter is explicitly provided
  • Saves to both main folder AND project folder

Finding Sessions

Sessions are organized in topic-named folders:
  • Browse: ~/.codearchitect/sessions/YYYY-MM-DD/topic-folder/
  • Search: grep -r "keyword" ~/.codearchitect/sessions/
  • Git: Commit sessions for version control
  • Use folder names: Sessions are stored by topic, making them easy to find

Technical

Tech Stack: TypeScript, Node.js 18+, MCP SDK License: CC-BY-NC-4.0 (free for non-commercial use) Status: Production-ready. Actively developed.

Getting Help