mcpField
S

Stellar Memory

Local
@sangjun0000Memory & Knowledge

About Stellar Memory

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

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "sangjun0000-stellar-memory": {
      "command": "npx",
      "args": [
        "-y",
        "stellar-memory"
      ],
      "env": {
        "STELLAR_PROJECT": "<STELLAR_PROJECT>",
        "STELLAR_DB_PATH": "<STELLAR_DB_PATH>",
        "STELLAR_API_PORT": "<STELLAR_API_PORT>",
        "STELLAR_SUN_TOKEN_BUDGET": "<STELLAR_SUN_TOKEN_BUDGET>"
      }
    }
  }
}
Run commandnpx -y stellar-memory
Environment variables to set
STELLAR_PROJECTActive project name for memory isolation
STELLAR_DB_PATHPath to SQLite database file (default: ~/.stellar-memory/stellar.db)
STELLAR_API_PORTREST API port (default: 21547)
STELLAR_SUN_TOKEN_BUDGETSecretMax tokens for Sun context (default: 800)

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmstellar-memory1.0.3

Tools

16

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
showenumNoShow memories, data sources, or both.memories | sources | all
zoneenumNoFilter to a specific orbital zone.all | core | near | active | archive | fading | forgotten
limitintegerNoMax memories to return.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.