Memory

com.cortex-memPublished by cortex-mem.comv1.2.5Updated Oct 24, 2026

Shared, persistent memory for AI agents — works with Claude, Kiro, Cursor, or any MCP client.

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

A local MCP server that gives AI agents shared, persistent memory across sessions and across MCP clients such as Claude, Kiro and Cursor.

What you can do
Provides persistent memory that an assistant can keep across sessions rather than losing when a conversation ends. Shares that memory between different MCP clients, so context stored in one tool can be available in another. Runs as a local process on the user's machine, so memory is tied to that machine. No individual tools are documented in the supplied material, so specific operations cannot be described.
When to use it
Worth considering when you want an assistant to remember information between conversations, or when you use several MCP clients and want them to draw on the same stored context.
Requirements
Runs as a local process over stdio, installed from the npm package cortex-memory-mcp, so a Node.js runtime and npm are needed on the user's machine. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
Persistent memory means whatever the assistant stores may be retained on the local machine and shared with other connected MCP clients; review what gets saved. The supplied material does not document storage location, retention, deletion or encryption, so check these before storing sensitive information.

Installation

In SourceWeft

  1. Open Memory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.2.5LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Memory integrations