Give your AI a permanent memory in under 2 minutes. Works with any AI that supports MCP — Claude, ChatGPT, DeepSeek, Gemini, Mistral, Cursor, local models, and more.
MCP = Model Context Protocol — the standard way AI apps connect to local tools.Before you start: Make sure SAGE is running. If you installed the app, just open it. If you built from source, run sage-gui serve. You should see the CEREBRUM at http://localhost:8080/ui/
In Claude Desktop: Settings → Developer → Edit Config.
This opens a JSON file called claude_desktop_config.json.
Add this to the file (replace the entire contents if it's empty):
{
"mcpServers": {
"sage": {
"command": "/Applications/SAGE.app/Contents/MacOS/sage-gui",
"args": ["mcp"],
"env": {
"SAGE_HOME": "~/.sage",
"SAGE_PROVIDER": "claude-desktop"
}
}
}
}
"command": "C:\\Program Files\\SAGE\\sage-gui.exe"
Quit and reopen Claude Desktop. You should see a tools icon (hammer) in the chat — click it to verify SAGE tools are listed.
Start a new conversation and type:
Take the red pill. Initialize your SAGE memory.
If you installed from the DMG, it's inside the app bundle. If you built from source, it's wherever you put it.
# macOS (DMG install):
/Applications/SAGE.app/Contents/MacOS/sage-gui
# Built from source:
which sage-gui
Create a .mcp.json file in your project root:
{
"mcpServers": {
"sage": {
"command": "/Applications/SAGE.app/Contents/MacOS/sage-gui",
"args": ["mcp"],
"env": {
"SAGE_HOME": "~/.sage",
"SAGE_PROVIDER": "claude-code"
}
}
}
}
Close and reopen Claude Code (or start a new terminal session). SAGE tools will appear automatically.
Tell Claude:
Take the red pill. Initialize your SAGE memory.
CLAUDE.md file to your project with: "Call sage_turn every turn to maintain persistent memory." This ensures Claude never forgets to save its experience.
Settings → Beta Features → enable Developer Mode. Then go to Settings → Developer and add an MCP server.
Paste this MCP config:
{
"mcpServers": {
"sage": {
"command": "/Applications/SAGE.app/Contents/MacOS/sage-gui",
"args": ["mcp"],
"env": {
"SAGE_HOME": "~/.sage",
"SAGE_PROVIDER": "chatgpt"
}
}
}
}
"command": "C:\\Program Files\\SAGE\\sage-gui.exe"
Quit and reopen the ChatGPT app. Start a new conversation and say:
Take the red pill. Initialize your SAGE memory. Use sage_turn every reply to remember our conversations.
Install the MCP SuperAssistant Chrome extension. It bridges MCP tools between your browser and local services.
Open the extension sidebar and add a new MCP server:
Command: /Applications/SAGE.app/Contents/MacOS/sage-gui
Arguments: mcp
Environment:
SAGE_HOME=~/.sage
SAGE_PROVIDER=chatgpt
Open chat.openai.com in Chrome and chat normally. The extension handles the rest. Tell ChatGPT:
Take the red pill. You have SAGE memory tools. Use sage_turn every reply to build persistent memory.
sage-gui mcp.
Most MCP-compatible tools have a JSON config file or settings panel for MCP servers. Check your tool's documentation for where to add MCP server configs.
The config is the same everywhere — just change the SAGE_PROVIDER to match your tool:
{
"mcpServers": {
"sage": {
"command": "/path/to/sage-gui",
"args": ["mcp"],
"env": {
"SAGE_HOME": "~/.sage",
"SAGE_PROVIDER": "your-tool-name"
}
}
}
}
cursor, windsurf, etc. Facts (verified truths) are shared across all providers automatically.
Restart your AI tool, then tell it:
Call sage_red_pill to initialize your memory. Then call sage_turn every reply.
Make sure SAGE is running — check http://localhost:8080/ui/ in your browser. If the CEREBRUM loads, SAGE is running. Also verify the path to sage-gui in your config is correct.
SAGE runs on port 8080 by default. Make sure no other app is using that port, and that SAGE was started before your AI tool.
This usually means the embedding provider isn't configured. Open the SAGE app (or run sage-gui setup) to re-run the setup wizard. Pick "Hash" for zero-setup or "Ollama" for semantic search.
Yes! That's what SAGE_PROVIDER is for. Each tool gets its own memory space. Set different provider names in each config. Facts are shared; personal observations and reflections stay scoped to each tool.
Everything stays on your machine in ~/.sage/. The database is a single SQLite file. Nothing is ever sent to any cloud. If you enabled encryption during setup, all memories are AES-256-GCM encrypted at rest.
Absolutely. SAGE is model-agnostic — your memories belong to you, not to any provider. Just add the config to your new tool and your AI picks up where the last one left off. Facts are shared across providers automatically.