Skip to main content
Glama
CodeArchitect MCP

CodeArchitect MCP

by tairqaldy

CodeArchitect MCP

Your AI conversations shouldn't disappear. CodeArchitect MCP automatically saves and retrieves your discussions with AI assistants, solving context continuity for developers. Never re-explain architecture decisions or code solutions. Built on Model Context Protocol (MCP) - works seamlessly with Cursor and VS Code. Expanding into comprehensive system design and architecture assistance.

Quick Start

1. Install Node.js

Download from nodejs.org (v18+). Open terminal → type node --version to verify.

2. Install Package

npm install -g codearchitect-mcp

3. Configure IDE

Step 1: Open Cursor Settings

  1. Open Cursor (the code editor)

  2. Look at the bottom left corner - click the gear icon ⚙️ (or press Ctrl+, on Windows/Linux, Cmd+, on Mac)

  3. This opens Settings

Step 2: Find MCP Settings

  1. In the Settings search box at the top, type: "MCP" or "Model Context Protocol"

  2. You should see "Tools & MCP" section

  3. Click on it

Step 3: Add CodeArchitect Server

  1. Look for "MCP Servers" or "Add Server" button

  2. Click "Add Server" or the + button

  3. A form will appear. Fill it in:

    • Name: codearchitect (or any name you like)

    • Command: npx

    • Args: -y codearchitect-mcp@latest

  4. Click Save or OK

OR (Alternative Method - Manual Config File):

  1. Close Cursor

  2. Open File Explorer (Windows) or Finder (Mac)

  3. Go to your home folder:

    • Windows: C:\Users\YourName\.cursor\ (create .cursor folder if it doesn't exist)

    • Mac/Linux: ~/.cursor/ (create .cursor folder if it doesn't exist)

  4. Create a file named mcp.json in that folder

  5. Open it in any text editor and paste this:

{
  "mcpServers": {
    "codearchitect": {
      "command": "npx",
      "args": ["-y", "codearchitect-mcp@latest"]
    }
  }
}
  1. Save the file

  2. Open Cursor again

Step 4: Verify It's Working

  1. In Cursor, look at the bottom status bar

  2. You should see "MCP" or "codearchitect" with a green dot (connected)

  3. If you see red or yellow, something went wrong - see troubleshooting below

Step 5: Reload Cursor

  1. Press Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (Mac)

  2. Type: "Reload Window"

  3. Press Enter

  4. Cursor will restart - wait for it to finish loading

Step 6: Test It Works

  1. Open any chat/conversation in Cursor

  2. Type: "use codearchitect"

  3. You should see a list of features and workflow guide

  4. If you see an error, see troubleshooting below

Export Chat (How to Save Conversations)

  1. In Cursor chat, look at the top right corner

  2. Click the three dots menu (⋯)

  3. Click "Export Chat"

  4. A save dialog appears

  5. Navigate to: C:\Users\YourName\.codearchitect\exports\ (Windows) or ~/.codearchitect/exports/ (Mac/Linux)

    • Create the exports folder if it doesn't exist

  6. Click Save

  7. The file will be saved as .md format (that's normal)

Need Help?

Stuck at any step? Reach out to Tair:

Step 1: Open Command Palette

  1. Open VS Code (Visual Studio Code)

  2. Press Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (Mac)

  3. A box appears at the top - this is the Command Palette

Step 2: Add MCP Server

  1. In the Command Palette box, type: "MCP: Add Server"

  2. You should see "MCP: Add Server..." appear in the list

  3. Click it (or press Enter)

Step 3: Choose Installation Method

  1. A menu appears asking how to install

  2. Choose: "Download with npm package" (click it)

  3. Another box appears asking for the package name

Step 4: Enter Package Name

  1. Type exactly: codearchitect-mcp

  2. Press Enter

  3. VS Code will download and install it (wait a few seconds)

Step 5: Verify It's Working

  1. Look at the bottom right corner of VS Code

  2. You should see "MCP" or "codearchitect" with a green indicator (connected)

  3. If you see red or an error, see troubleshooting below

Step 6: Reload VS Code

  1. Press Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (Mac) again

  2. Type: "Developer: Reload Window"

  3. Press Enter

  4. VS Code will restart - wait for it to finish

Step 7: Test It Works

  1. Open any chat/conversation in VS Code

  2. Type: "use codearchitect"

  3. You should see a list of features and workflow guide

  4. If you see an error, see troubleshooting below

Export Chat (How to Save Conversations)

  1. In VS Code chat, press Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (Mac)

  2. Type: "Export Chat"

  3. Click "Export Chat" from the list

  4. A save dialog appears

  5. IMPORTANT: Name your file something meaningful, like:

    • auth-implementation.json

    • database-design.json

    • api-routes.json

    • (Use .json at the end - VS Code will add it automatically)

  6. Navigate to: C:\Users\YourName\.codearchitect\exports\ (Windows) or ~/.codearchitect/exports/ (Mac/Linux)

    • Create the exports folder if it doesn't exist

  7. Click Save

  8. The file will be saved as .json format (that's normal - CodeArchitect supports this!)

Need Help?

Stuck at any step? Reach out to Tair:

4. Verify Setup

  • Check MCP status: Should show green/connected in IDE

  • Test: Say "use codearchitect" - should see features list

  • If not working: Reload IDE and check MCP logs / Reach out to Tair

5. Start Using

  • "use codearchitect" - See features and workflow guide

  • "use codearchitect store_session" - Save conversation

  • "use codearchitect get_session" - Retrieve session

  • "use codearchitect search_session [query]" - Search across all sessions

Related MCP server: Memory MCP Server

Storage

Main location: ~/.codearchitect/sessions/ (always)

  • Windows: C:\Users\YourName\.codearchitect\sessions\

  • Linux/Mac: ~/.codearchitect/sessions/

Optional: Also save to project folder (specify projectDir)

Exports: ~/.codearchitect/exports/ (for export file detection)

Workflow

  1. Export chat → Save to ~/.codearchitect/exports/

  2. Store session → "use codearchitect store_session"

  3. Retrieve → "use codearchitect get_session [topic]"

  4. Search → "use codearchitect search_session [query]" - Find sessions by keyword

  5. Repeat → Build knowledge base iteratively

Docs


Made with ❤️ by Tair Kaldybayev

Available Tools

4 tools
codearchitect_helpA

Get help about CodeArchitect MCP features. Use when user says "use codearchitect" without specifying a feature, or asks "what can codearchitect do?". Returns available features with examples and next steps.

Inputs: feature.

get_sessionA

[CodeArchitect] Retrieve previous conversations to avoid re-explaining.

=== WHEN TO USE ===

  • User says: "use codearchitect get_session", "get that previous conversation", "retrieve session"

  • User mentions something they discussed before

  • User wants to continue work on a previous topic

=== STORAGE BEHAVIOR ===

  • Always retrieves from main folder: ~/.codearchitect/sessions/ (user's home directory)

  • No project detection - all sessions are in main folder

=== USAGE ===

  • No parameters: Lists all sessions

  • filename: Get specific session by topic folder name

  • date: List sessions from specific date (YYYY-MM-DD format)

  • limit: Limit number of results when listing

Inputs: date, limit, format, filename.

search_sessionA

[CodeArchitect] Search across all stored sessions to find relevant conversations.

=== WHEN TO USE ===

  • User says: "use codearchitect search_session [query]", "search for [topic]", "find sessions about [topic]"

  • User wants to find sessions by keyword or topic

  • User remembers discussing something but not the exact session name

=== STORAGE BEHAVIOR ===

  • Always searches in main folder: ~/.codearchitect/sessions/ (user's home directory)

  • Searches through all date folders unless filtered

=== SEARCH BEHAVIOR ===

  • Full-text search across topic, content, and messages

  • Case-insensitive matching

  • Returns relevance scores and context snippets

  • Results sorted by relevance (highest first), then by date (newest first)

=== PARAMETERS ===

  • query (required): Search query string

  • date (optional): Filter by specific date (YYYY-MM-DD format)

  • dateFrom (optional): Filter from date (YYYY-MM-DD format)

  • dateTo (optional): Filter to date (YYYY-MM-DD format)

  • limit (optional): Limit number of results returned

=== RESPONSE === Returns matching sessions with:

  • Relevance score (0-1)

  • Matched snippets showing context

  • Match count

  • Session metadata (topic, date, filename)

Inputs: query (required), date, limit, dateTo, +1 more.

store_sessionA

[CodeArchitect] Save important conversations for future reference.

=== WHEN TO USE ===

  • User says: "use codearchitect store_session", "save this conversation", "store this", "remember this"

  • User wants to keep/remember an important discussion

  • After solving complex problems or making architecture decisions

=== STORAGE BEHAVIOR ===

  1. ALWAYS saves to main folder: ~/.codearchitect/sessions/ (user's home directory)

  2. OPTIONALLY saves to project folder if user specifies projectDir parameter

  3. NEVER auto-detects project - only use projectDir if user explicitly provides it

=== CONVERSATION SOURCE (CHOOSE ONE) ===

OPTION 1: Export File (RECOMMENDED - Most Reliable)

  • User exports conversation from Cursor/VS Code to .codearchitect/exports/ folder

  • Tool automatically detects and processes the export file

  • No need to manually extract conversation

WORKFLOW:

  1. User exports chat: In Cursor/VS Code → three dots (⋯) → "Export Chat"

  2. User saves to: ~/.codearchitect/exports/ folder (main location - always the same)

  3. User says: "use codearchitect store_session"

  4. Tool automatically finds newest export file and stores it

If multiple exports exist:

  • Tool processes newest file (modified in last 10 minutes)

  • If user wants specific file: use exportFilename parameter (e.g., "resolve_mcp")

OPTION 2: Direct Conversation Parameter (Fallback)

  • Only use if export file method doesn't work

  • Extract FULL conversation from your context window

  • Format as plain text with USER/ASSISTANT markers OR JSON array

=== PARAMETERS ===

  • conversation (optional): Direct conversation text/JSON - only use if export file unavailable

  • exportFilename (optional): Pattern to match specific export file (e.g., "resolve_mcp" matches "cursor_resolve_mcp_configuration_issues.md")

  • topic (optional): Session topic - auto-extracted if not provided

  • projectDir (optional): Project directory path - if provided, saves to both main and project folders

  • format (optional): "plain" or "messages" - default "plain"

=== WORKFLOW (EXPORT METHOD) === Step 1: User exports conversation to ~/.codearchitect/exports/ folder (main location) Step 2: User says "use codearchitect store_session" Step 3: Tool detects export file automatically from main exports folder Step 4: Tool parses and stores conversation Step 5: Tool saves to main sessions folder (always) + optionally project folder if projectDir specified

=== ERROR HANDLING === If no export file found:

  • Return clear instructions with OS/IDE-specific export folder path

  • Tell user exactly where to save the export file

  • Provide step-by-step instructions

=== RESPONSE === After saving, return concise message:

  • "Detected export file '[filename]', saved to main: [topic-name]. Next: use codearchitect get_session [topic-name]"

  • Or if projectDir provided: "Detected export file '[filename]', saved to main: [topic-name] and project: [topic-name]. Next: use codearchitect get_session [topic-name]"

Inputs: topic, format, projectDir, conversation, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: help provides guidance, store saves sessions, get retrieves sessions, and search finds sessions by content. No overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: codearchitect_help, store_session, get_session, search_session. The convention is uniform and predictable.

    Tool Count5/5

    With 4 tools covering help, store, get, and search, the set is well-scoped for session management. Neither too few nor too many tools for the domain.

    Completeness4/5

    The set covers the main lifecycle (store, get, search) and help, which is solid. Minor gaps exist like missing update or delete operations, but the core functionality is complete for session storage and retrieval.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers