Mem
for LuumenAI
Search your Mem notes for context, then file new ones as approved steps
Connect Mem and Luumen can read the notes your team already keeps — runbook fragments, postmortem drafts, meeting records — and pull them into a terminal session without you switching windows. Searches and reads answer right away. Creating a note or a collection is previewed first, then written on your approval. Luumen connects with an API key.
The Mem toolbox
11 tools: 6 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet CollectionRetrieve the details of a Mem collection by its UUID.
- ReadList CollectionsList collections with pagination support.
- ReadList NotesList notes with pagination and filtering options.
- ReadRead NoteRetrieve the content and metadata of a Mem note by its UUID.
- ReadSearch CollectionsSearch collections using an optional query string.
- ReadSearch NotesSearch notes in Mem using a query string with optional filtering.
- WriteCreate CollectionCreates a new collection in Mem for organizing and grouping related notes. Approval by default
- WriteCreate Note V2Create a new note with markdown content and optional collection associations. Approval by default
- WriteDelete CollectionPermanently delete a Mem collection. Approval by default
- WriteDelete NotePermanently delete a specific note. Approval by default
- WriteSave ContentProcess and remember any raw content using AI. Approval by default
One prompt, start to finish
What a governed Mem run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create collection, create note v2, delete collection, delete note, and more — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Mem — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
ConfluenceSOPs and runbooks that become skills the whole team can run.
NotionRunbooks in Notion, followed and turned into skills.
SharePointRead SharePoint sites for context, then change files and permissions on approval.
Google DriveSearch Drive for the file you need, then write the change back as an approved stepPut Mem to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.