Skip to main content
Glama

Cursor-Cortex: Structured Memory for AI Assistants

Works with Cursor, Claude Code, and any MCP-compatible AI assistant.

Solve AI assistant memory loss and context confusion. Cursor-Cortex gives your AI the structured thinking and long-term memory it needs to actually help you build software.

🧠 The Problem with AI Assistants

LLM-based AI assistants are amazing at generating code and explaining concepts, but they struggle with:

  • ❌ Memory Loss: "What were we working on yesterday?"

  • ❌ Context Switching: "Wait, what is this project about again?"

  • ❌ Agent Failures: Getting lost, hallucinating, losing track of goals

  • ❌ No Structure: Jumping between ideas without systematic thinking

  • ❌ Knowledge Gaps: No access to company-specific or project-specific insights

Result: You spend more time explaining context than actually solving problems.

Related MCP server: ContextStream MCP Server

🎯 The Cursor-Cortex Solution

Cursor-Cortex provides your AI with structured external memory:

📋 Context Files → "What is this project about?"

Your AI always knows the project goals, architecture decisions, and current focus.

📝 Branch Notes → "What have we been working on?"

Continuous development log so your AI can pick up exactly where you left off.

🧠 Tacit Knowledge → "How do we solve this type of problem?"

Company-specific solutions, patterns, and hard-won insights that LLMs don't know.

✅ Checklists → "What's our systematic approach?"

Structured thinking frameworks that keep AI (and you) organized and thorough.

💡 Before vs After

❌ Without Cursor-Cortex:

You: "Help me continue the authentication work"
AI: "I need more context. What authentication system? What issues were you facing?"
You: "Ugh, let me explain everything again..."

✅ With Cursor-Cortex:

You: "Help me continue the authentication work"  
AI: *reads context + branch notes + knowledge base*
"I see you're implementing JWT refresh tokens and hit CORS issues yesterday. 
Based on our company knowledge doc about API security, let's check the middleware..."

🚀 Core Benefit

Turn your AI from a smart intern into an experienced teammate who remembers everything, follows structured thinking, and has access to institutional knowledge.

⚡ Complete Setup Guide

1. Install Dependencies

npm install --legacy-peer-deps

Note: The --legacy-peer-deps flag is required due to TensorFlow.js peer dependency conflicts between v3.x and v4.x versions.

2. Get Full Path

pwd
# Copy the output - you'll need it for configuration

3. Vector Search Setup (Optional)

For AI-powered semantic search capabilities:

System Requirements:

  • Node.js 18+

  • 2GB RAM for vector models

  • 500MB disk space

Setup Steps:

# Step 1: Generate embeddings for all knowledge files
node generate-all-embeddings-cpu.js

# This creates vector embeddings for:
# - All tacit knowledge documents
# - All branch notes
# - All context files
# Duration varies by document count and system specs

# Step 2 (Optional): Force regenerate if content changes
node generate-all-embeddings-cpu.js --force

# Step 3 (Optional): View progress during generation
node generate-all-embeddings-cpu.js --verbose

Why This Matters:

  • Without embeddings, semantic search falls back to text search

  • Pre-computed embeddings make searches 100x faster

  • Generate once, use for all semantic queries

  • Embeddings stored in ~/.cursor-cortex/embeddings/

4. Configure Cursor MCP

Create or edit ~/.cursor/mcp.json:

"cursor-cortex": {
      "command": "node",
      "args": ["/YOUR/FULL/PATH/TO/cursor-cortex/index.js"],
      "tools": [
        "update_branch_note", 
        "add_commit_separator",
        "read_branch_notes",
        "update_context_file", 
        "read_project_context",
        "read_branch_context", 
        "list_context_files", 
        "generate_commit_message", 
        "generate_jira_comment", 
        "create_tacit_knowledge",
        "read_tacit_knowledge", 
        "search_branch_notes",
        "generate_embeddings",
        "create_completion_checklist",
        "read_checklist",
        "update_checklist",
        "sign_off_checklist",
        "archive_branch_note",
        "clear_branch_note",
        "list_all_branch_notes",
        "enhanced_branch_survey",
        "comprehensive_knowledge_search",
        "construct_project_narrative",
        "timeline_reconstruction",
        "context_sync_guidance",
        "analyze_documentation_gaps",
        "migrate_context_files",
        "request_critical_thinking_space",
        "check_critical_thinking_status",
        "request_thinking_guidance",
        "add_perspective",
        "request_synthesis_space",
        "request_synthesis_step_guidance",
        "complete_synthesis_step",
        "generate_context_zip",
        "unpack_context"
      ],
      "stdio": true,
      "env": {
        "DEBUG": "true"
      }
    },

Replace /YOUR/FULL/PATH/TO/cursor-cortex/ with the output from step 2

Note: This configuration is for Cursor-Cortex v1.2.0+. If you're using an older version, some tools may not be available. Check your package.json version and consider updating.

5. Restart Cursor

Close and reopen Cursor completely.


Claude Code Installation

Create or edit .claude/settings.json in your project root (or ~/.claude/settings.json globally):

{
  "mcpServers": {
    "cursor-cortex": {
      "command": "node",
      "args": ["/YOUR/FULL/PATH/TO/cursor-cortex/index.js"]
    }
  }
}

Replace /YOUR/FULL/PATH/TO/cursor-cortex/ with the output from step 2, then restart Claude Code.


6. Enable MCP Server

  1. Go to Cursor Settings (Cmd/Ctrl + ,)

  2. Navigate to Features → Model Context Protocol

  3. Find cursor-cortex and toggle it ON

  4. You should see: Storage directory created at /Users/yourname/.cursor-cortex

7. Test It

In any Cursor chat, try:

"Update my branch notes: Testing Cursor-Cortex setup"

If it works, you'll see: Successfully updated branch note with: "Testing Cursor-Cortex setup"

8. Knowledge Explorer (Visual Graph)

Once everything is set up, explore your knowledge base as an interactive network graph:

npm run explorer

Then open http://localhost:4000 in your browser.

Features:

  • Three-tier visualization: Projects, branch notes, and tacit knowledge as interconnected nodes

  • Similarity-driven layout: Semantically similar projects cluster together using embedding cosine similarity

  • Neural pulse animation: Watch signals propagate through your knowledge network in real-time

  • Activity-based colors: Brighter nodes = more recently updated projects

  • Click to explore: Click any node to see details, similar projects, and tags

  • Depth toggle: Switch between Compact (projects only), Branches, and Full views

🔧 Troubleshooting

Common Issues:

❌ "Tool not found" error

  • Restart Cursor completely after configuration

  • Verify MCP server is enabled in settings

  • Check file path in mcp.json is correct (no typos)

❌ MCP configuration not working

  • Validate JSON syntax at jsonlint.com

  • Ensure commas and quotes are correct

  • Check file permissions on mcp.json

❌ Vector search not working

  • Run npm install to ensure TensorFlow.js is installed

  • Check system has 2GB+ RAM available

  • Try text search mode if vector search fails

Need Help? Create an issue with your error message for quick support.

9. Start Using

  • "Show my uncommitted work" - See what you've been working on

  • "Generate a commit message" - Create commits from your notes

  • "Create tacit knowledge document" - Save solutions for later

📖 Basic Usage

Capture Your Thoughts

As you code, tell your AI assistant:

"Update branch notes: Fixed the login validation bug by adding proper error handling 
for expired tokens. Had to modify the JWT middleware."

Stay Oriented

When you return to work:

"Show me my uncommitted work"

Smart Commits

When ready to commit:

"Generate a commit message"

AI reads all your notes and creates: "Fix JWT token validation and error handling"

🏗️ Project Structure

Cursor-Cortex organizes your knowledge into:

  • 📝 Branch Notes: What you're working on right now

  • 📋 Context Files: Project documentation and decisions

  • 🧠 Knowledge Base: Solutions and insights for future reference

  • ✅ Checklists: Track project completion

All stored in ~/.cursor-cortex/ and accessible through AI.


🎓 Power User Features

Once you're comfortable with basics, explore these advanced capabilities:

"Search all my projects for JWT authentication solutions"

Automatic Commit Tracking

node setup-hooks.js  # Auto-separates pre/post commit work

Project Checklists

Track requirements, testing, and sign-offs:

"Create a completion checklist for the user auth feature"

Team Knowledge Sharing

Create reusable solution documents:

"Create tacit knowledge document about our JWT implementation approach"

Knowledge Archaeology & Project Intelligence

Analyze and synthesize project knowledge:

"Survey all my branch documentation and show completeness scores"
"Construct a project narrative for the user authentication system"
"Show me a timeline of all development across projects"
"Analyze this folder structure for documentation gaps"

🛠️ All Available Tools

  • update_branch_note - Add entries to your development log

  • read_branch_notes - Default is the full file (including COMMIT separators); mode=uncommitted or uncommittedOnly=true for work since the last commit; optional beforeDate, afterDate, or commitHash to filter

  • add_commit_separator - Mark commit boundaries (auto via git hooks)

  • generate_commit_message - AI creates commits from your notes

  • update_context_file - Document project goals and decisions

  • read_project_context - Read branch-agnostic project context only

  • read_branch_context - Read branch-specific context only

  • list_context_files - Browse all project docs with cross-project warnings

  • create_tacit_knowledge - Document solutions for future reference

  • read_tacit_knowledge - Search knowledge across all projects with tags and content search

  • search_branch_notes - Search branch notes across projects with semantic search

  • generate_embeddings - Generate or regenerate vector embeddings for semantic search

  • comprehensive_knowledge_search - Global semantic search across ALL Cursor-Cortex knowledge

  • create_completion_checklist - Track requirements and deliverables

  • read_checklist - View progress

  • update_checklist - Mark items completed (manual or auto-detect)

  • sign_off_checklist - Formal approval with signatures

  • archive_branch_note - Archive completed work

  • clear_branch_note - Reset branch documentation

  • migrate_context_files - Migrate existing context files to Smart Hybrid Context System

  • list_all_branch_notes - View all branch notes across all projects with priority ordering

  • enhanced_branch_survey - Comprehensive analysis of documentation with completeness scoring and relationship mapping

  • construct_project_narrative - Weave scattered technical details into coherent production stories

  • timeline_reconstruction - Extract chronological timeline data from branch notes and commit separators

  • context_sync_guidance - Get contextual guidance for syncing project contexts based on timeline data

  • analyze_documentation_gaps - Analyze folder structure to identify documentation needs and auto-create checklists

  • request_critical_thinking_space - Create systematic analysis workspace using Six Thinking Hats methodology

  • check_critical_thinking_status - Check completion status of critical thinking analysis

  • request_thinking_guidance - Get guidance for specific Six Thinking Hats perspectives

  • add_perspective - Add specific perspective analysis to critical thinking workspace

  • request_synthesis_space - Load perspectives into synthesis workspace for integration

  • request_synthesis_step_guidance - Get detailed guidance for synthesis steps

  • complete_synthesis_step - Complete specific synthesis step and update process

  • generate_context_zip - Package knowledge into portable ZIP archive for sharing between users/environments

  • unpack_context - Import shared context package with safe conflict resolution

🎛️ Advanced Configuration

Git Integration

Automatic commit separators require the MCP server to be running:

node setup-hooks.js  # Install git hooks

CLI Interface

Direct access without AI:

node cursor-cortex-cli.js  # Interactive menu

🤝 Contributing

Found a bug or have an idea? Open an issue or submit a pull request — contributions are welcome!

Author: Manuel Flores-Ramirez

📄 License

This project is licensed under the Parachute Public License (PPL) v1.0.

The PPL is an ethical license that includes restrictions against use by government, military, surveillance, and other harmful entities. For full details and rationale, see parachute.pub.

© 2025 Manuel Flores-Ramirez.

Available Tools

38 tools
add_commit_separatorC

Add a commit separator to the branch note with commit metadata

Inputs: branchName (required), commitHash (required), projectName (required), commitMessage (required).

add_perspectiveA

Add a specific Six Thinking Hats perspective analysis to critical thinking workspace. REQUIRES calling request_thinking_guidance first for this perspective - will fail if guidance not requested.

Inputs: analysis (required), analysisId (required), perspective (required), projectName (required).

analyze_documentation_gapsC

Analyzes folder structure to identify documentation needs and create knowledge capture checklists. Phase 2.3 of Knowledge Archaeology & Reality Sync Engine.

Inputs: folderPath (required), projectName (required), maxDepth, includeTests, +3 more.

archive_branch_noteC

Archive branch notes for a project

Inputs: branchName (required), projectName (required), archiveDate.

check_critical_thinking_statusA

Check the completion status of a critical thinking analysis. Shows which Six Thinking Hats perspectives are complete and which are missing. Prevents rushed decisions by clearly showing incomplete analysis.

Inputs: analysisId (required), projectName (required).

clear_branch_noteA

Clear branch notes for a project, optionally creating an archive first

Inputs: branchName (required), projectName (required), keepHeader, createArchive.

complete_synthesis_stepA

Complete a specific synthesis step and update the synthesis process. REQUIRES calling request_synthesis_step_guidance first for this step - will fail if guidance not requested.

Inputs: step (required), analysis (required), analysisId (required), projectName (required).

construct_project_narrativeC

Phase 2.1: Narrative Construction Engine - Weaves scattered technical details into coherent production stories using Knowledge Archaeology techniques

Inputs: projectName (required), branchName, narrativeType, includeContext, +1 more.

context_sync_guidanceC

Provides contextual guidance for syncing project contexts based on timeline data and sync type

Inputs: syncType (required), projectName (required), branchName, timelineData.

create_completion_checklistB

Create a project completion checklist using the Cursor-Cortex template

Inputs: owner (required), objectives (required), featureName (required), projectName (required), +4 more.

create_tacit_knowledgeC

Create a tacit knowledge document based on the Cursor-Cortex template

Inputs: title (required), author (required), outcome (required), approach (required), +7 more.

enhanced_branch_surveyB

Semantic-first branch survey system for Knowledge Archaeology - provides comprehensive analysis using semantic search across all branches with completeness scoring, relationship mapping, and production readiness assessment. Uses AI-powered semantic understanding by default.

Inputs: currentProject, conceptualQuery, includeAnalysis, semanticAnalysis, +3 more.

generate_commit_messageB

Generate a commit message based on the branch note without making the commit

Inputs: branchName (required), projectName (required), jiraTicket.

generate_context_zipA

Package Cursor-Cortex knowledge into a portable ZIP archive for sharing between users and environments

Inputs: outputPath (required), description, includeTypes, projectNames, +1 more.

generate_embeddingsA

Generate or regenerate vector embeddings for all Cursor-Cortex knowledge files (tacit knowledge, branch notes, context files). Enables semantic search across entire knowledge base.

Inputs: verbose, projectName, forceRegenerate.

generate_jira_commentA

Generate a comment for a Jira ticket about the changes without updating the ticket

Inputs: ticketId (required), branchName (required), projectName (required), jiraBaseUrl.

graphql_knowledge_queryA

Query the GraphQL Knowledge Hub API for structured knowledge discovery, project graph traversal, pipeline exploration, and cross-project relationship analysis. Requires the GraphQL server to be running (node graphql/server.cjs).

Inputs: query (required), endpoint, variables.

list_all_branch_notesA

List all branch notes across all projects, grouped by branch with priority order (main, stage, then alphabetically). Use maxItems to only include the most recently modified note files (reduces noise).

Inputs: maxItems, includeEmpty, currentProject.

list_context_filesB

List all context files for a project or across all projects

Inputs: projectName (required), listAll, currentProject.

migrate_context_filesA

Migrate existing context files to the Smart Hybrid Context System. Converts main/master contexts to project_context.md and preserves branch-specific contexts.

Inputs: projectName (required), dryRun, createBackup, migrationStrategy.

read_branch_contextB

Read branch-specific context file (current branch context only)

Inputs: branchName (required), projectName (required), currentProject.

read_branch_notesB

Read branch notes - defaults to showing uncommitted work, can also filter by commit hash or date range

Inputs: branchName (required), projectName (required), afterDate, beforeDate, +2 more.

read_checklistC

Read a completion checklist for the project

Inputs: projectName (required), checklistName.

read_pipeline_contextB

Read pipeline-specific context file

Inputs: projectName (required), pipelineName (required), currentProject.

read_project_contextA

Read project context file (branch-agnostic, shared across all branches)

Inputs: projectName (required), currentProject.

read_tacit_knowledgeB

Read tacit knowledge documents with optional semantic search - supports exact filename access, text search, or vector-based semantic search for concept retrieval

Inputs: projectName (required), searchTags, searchTerm, crossProject, +3 more.

request_critical_thinking_spaceA

Create a new critical thinking analysis workspace using Six Thinking Hats methodology. This starts a multi-step systematic analysis process that enforces completion of all six perspectives before allowing final decisions. Returns an analysis ID for tracking progress.

Inputs: topic (required), projectName (required), context, analysisId.

request_synthesis_spaceA

Load all Six Thinking Hats perspectives into synthesis workspace and start stepped synthesis process. REQUIRES all 6 perspectives to be completed first. Sets up synthesis semaphore for systematic integration.

Inputs: analysisId (required), projectName (required).

request_synthesis_step_guidanceA

Request detailed guidance for a specific synthesis step. Shows prompts and questions to guide proper synthesis step completion. Must be called BEFORE complete_synthesis_step for that step.

Inputs: step (required), analysisId (required), projectName (required).

request_thinking_guidanceA

Request Six Thinking Hats guidance for a specific perspective before analysis. Shows thinking prompts and questions to guide proper analysis approach. Must be called BEFORE add_perspective for that hat color.

Inputs: analysisId (required), perspective (required), projectName (required).

search_branch_notesA

Search branch notes across projects with semantic search - find development insights, problem-solving journeys, and decision contexts

Inputs: searchTerm (required), sortBy, dateRange, branchName, +4 more.

sign_off_checklistC

Sign off on a completed checklist item

Inputs: projectName (required), signOffItem (required), checklistName (required), signatureName (required).

timeline_reconstructionA

Phase 2.2: Timeline Reconstruction Tool - Extracts chronological timeline data from branch notes and commit separators for reality sync analysis. OPTIMIZED: Now shows titles only for better performance and readability. Smart date filtering with shortcuts available. Returns scalable timeline with titles instead of full content.

Inputs: dateRange, branchName, projectName, includeCommits, +2 more.

unpack_contextA

Import shared context package and place content in appropriate Cursor-Cortex storage locations with safe conflict resolution

Inputs: zipPath (required), previewOnly, createBackup, conflictStrategy.

update_branch_noteC

Update the running note for the current branch with a new change entry

Inputs: message (required), branchName (required), projectName (required).

update_checklistB

Update checklist items based on branch context and progress

Inputs: projectName (required), checklistName (required), status, itemPath, +2 more.

update_context_fileC

Update the context file with information about the feature, pipeline, or project

Inputs: title (required), branchName (required), description (required), projectName (required), +8 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 38 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but a few like search_branch_notes and comprehensive_knowledge_search overlap in search functionality, and archive_branch_note/clear_branch_note both handle archiving. However, descriptions clarify boundaries well enough to avoid serious misselection.

    Naming Consistency3/5

    The server consistently uses snake_case, but conventions vary: many tools follow verb_noun (read_branch_notes, generate_commit_message) while others are noun phrases (enhanced_branch_survey, timeline_reconstruction, graphql_knowledge_query). This mixed pattern makes tool names slightly less predictable.

    Tool Count2/5

    With 38 tools, this server is over-scoped. Many tools are process sub-steps (e.g., request_thinking_guidance, add_perspective, complete_synthesis_step) that could be consolidated or parameterized. The high count increases cognitive load and feels excessive for a single MCP server.

    Completeness4/5

    The tool set covers the full knowledge lifecycle: creating, reading, updating, searching, archiving, and sharing knowledge, plus specialized analysis and decision workflows. Minor gaps exist (e.g., no delete for tacit knowledge, no update for context files after creation), but core workflows have no dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with persistent, searchable memory that survives across conversations using semantic search, temporal versioning, and smart organization. Enables long-term context retention and cross-session continuity for AI assistants.
      14
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Gives AI assistants persistent, queryable project memory for decisions, patterns, and rules, reducing the need to re-explain context in every prompt.
      11
      Apache 2.0