You’ll need a Nebula API key and collection ID before starting. Get both at trynebula.ai
Installation
One-Command Setup
ReplaceYOUR_API_KEY and YOUR_COLLECTION_ID, then paste into your Zo terminal:
~/.config/nebula/zo.env, configures MCPorter as the MCP bridge, and runs a test search.
Activating Memory
After installation, Zo defaults to its built-in rules system and will not use Nebula Memory automatically. You need to tell it to use the skill.- Create a Rule (Recommended)
- Mention Explicitly
Tell Zo to create a persistent rule so it always routes memory through Nebula:Once the rule exists, Zo searches on new conversations and stores after each exchange without further prompting.
Usage
What gets stored
- Preferences and conventions (“always use TypeScript”)
- Decisions and their reasoning (“chose Next.js App Router for RSC support”)
- Corrections and clarifications
- Project setup details and architecture notes
Skill CLI
Run search and store directly from the Zo terminal:search_memories and add_memory MCP tools described in the MCP integration guide.
File Locations
| File | Path | Purpose |
|---|---|---|
| Credentials | ~/.config/nebula/zo.env | API key and collection ID |
| MCPorter config | ~/.mcporter/mcporter.json | MCP server definition with auth headers |
| Skill instructions | /home/workspace/Skills/nebula-memory/SKILL.md | Teaches Zo’s AI when and how to use memory |
| Skill CLI | /home/workspace/Skills/nebula-memory/scripts/memory.sh | Bash wrapper for search and store |
Requirements
- Zo account
- Node.js (for MCPorter)
- jq