Stellar Memory

io.github.sangjun0000Published by GitHub account sangjun0000v1.0.3Updated Oct 24, 2026

Persistent AI memory using orbital mechanics. 100% local, zero API keys, MCP-native.

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

Stellar Memory gives an assistant a local, persistent memory store organized with an orbital-mechanics model, running entirely on the user's machine.

What you can do
Stellar Memory is a local MCP server that provides persistent memory for an AI assistant, described as using orbital mechanics to organize stored context. It runs as a local process over stdio and keeps its data in a SQLite database file. Configuration covers the REST API port, the database path, an active project name for memory isolation, and a token budget for context. No tool list is published in the manifest.
When to use it
Worth considering when an assistant should remember information across sessions and the user wants that memory kept locally rather than in a hosted service. The project setting suits keeping separate memory spaces for different work. It is desktop-only, so it is not for browser-based or remote use.
Requirements
Runs as a local process on the user's machine via the npm package stellar-memory over stdio, so Node.js is needed. Optional environment variables: STELLAR_API_PORT (default 21547), STELLAR_DB_PATH (default ~/.stellar-memory/stellar.db), STELLAR_PROJECT, and STELLAR_SUN_TOKEN_BUDGET (default 800). No authentication is declared.
Before you install
The server writes memory data to a local SQLite file at STELLAR_DB_PATH, so that file holds whatever the assistant stores and should be treated as private. It opens a local REST API port (STELLAR_API_PORT), which other local processes could reach. No API keys or credentials are requested, and no tool list is published, so review the actual tools before relying on it.

Installation

In SourceWeft

  1. Open Stellar 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.

Tools

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

Version history

1
  1. v1.0.3LatestSep 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