Read and curate the memory layer your agents run on, with writes held for approval
Mem0 holds the memory your LLM applications build up over time. Connect it and Luumen can read that memory in the terminal: search entries, look up a user, agent, app, or run, check export jobs, and review org and project membership. Changes — adding memory records, creating entities, granting project access — are previewed first and go out only after you approve. Luumen authenticates with an API key.
47 tools: 23 read, 24 write. Reads answer instantly. Writes require approval by default. Everything is logged.
ReadCreate memory entryLists/searches existing memory entries with filtering and pagination; critically, this action retrieves memories and does *not* create new ones, despite its name.
ReadExport data based on filtersCreates a new memory export job with optional entity filters (user_id, agent_id, app_id, run_id).
ReadList organizationsRetrieves a summary list of organizations for administrative oversight; returns summary data (names, IDs), not exhaustive details, despite 'detailed' in the name.
ReadFetch details of a specific organizationFetches comprehensive details for an organization using its `org_id`; the `org_id` must be valid and for an existing organization.
ReadGet list of entity filtersRetrieves predefined filter definitions for entities (e.g., by type, creation/modification date); returns definitions only, not filtered entity data.
ReadGet entity by idFetches detailed information for an existing entity (user, agent, app, or run) identified by its type and unique ID.
ReadGet event status by event IDRetrieves a single async event by ID to check its current status and results.
ReadGet memories by entityRetrieve all memories associated with a specific entity (user, agent, app, or run).
ReadGet memory exportRetrieves the status and results of a memory export job by its ID.
ReadGet organization membersFetches a list of members for a specified, existing organization.
ReadGet project detailsFetches comprehensive details for a specified project within an organization.
ReadGet project membersRetrieves all members for a specified project within an organization.
ReadGet projectsRetrieves all projects for a given organization `org_id` to which the caller has access.
ReadGet project webhooksRetrieves all webhooks configured for a specific project.
ReadGet user memory statsRetrieves a summary of the authenticated user's memory activity, including total memories created, search events, and add events.
ReadList entitiesRetrieves a list of entities, optionally filtered by organization or project (prefer `org_id`/`project_id` over deprecated `org_name`/`project_name`), noting results may be summaries and subject to…
ReadPerform semantic search on memoriesSearches memories semantically using a natural language query and metadata filters.
ReadRetrieve all events for the currently logged in userRetrieves a paginated list of events for the authenticated user, filterable and paginable via URL query parameters.
ReadRetrieve list of memory eventsRetrieves a chronological list of all memory events (e.g., user inputs, AI responses) from the Mem0 platform, providing interaction history and context for AI assistants.
ReadRetrieve memory by idRetrieves a complete memory entry by its unique identifier; `memory_id` must be valid and for an existing memory.
ReadRetrieve memory history by idRetrieves the complete version history for an existing memory, using its unique `memory_id`, to inspect its evolution or audit changes.
ReadRetrieve memory listRetrieves a list of memories, supporting pagination and diverse filtering (e.g., by IDs, metadata, keywords, date ranges); ensure dates are ISO 8601 and `page`/`page_size` (if used) are positive…
ReadSearch memories with filtersSemantically searches memories using structured filters with an optional natural language query.
WriteAdd member to projectAdds an existing user to a project (identified by `project_id` within organization `org_id`), assigning a valid system role. Approval by default
WriteAdd new memory recordsStores new memory records from a list of messages, optionally inferring structured content; requires association via `agent_id`, `user_id`, `app_id`, or `run_id`. Approval by default
WriteAdd organization memberAdds a new member, who must be a registered user, to an organization, assigning them a specific role. Approval by default
WriteCreate a new agentCreates a new agent with a unique `agent_id` and an optional `name`; additional metadata may be assigned by the system. Approval by default
WriteCreate a new agent runCreates a new agent run in the mem0.ai system. Approval by default
WriteCreate a new applicationCreates a new application, allowing metadata to be passed in the request body (not an explicit field in this action's request model); ensure `app_id` is unique to avoid potential errors or… Approval by default
WriteCreate a new organization entryCreates a new organization entry using the provided name and returns its details. Approval by default
WriteCreate a new userCreates a new user with the specified unique `user_id` and supports associating `metadata` (not part of the request schema fields). Approval by default
WriteCreate projectCreates a new project with a given name within an organization that must already exist. Approval by default
WriteCreate webhookCreates a new webhook for a specific project to receive real-time notifications. Approval by default
WriteDelete an organizationPermanently deletes an existing organization identified by its unique ID. Approval by default
WriteDelete memory by idPermanently deletes a specific memory by its unique ID; ensure the `memory_id` exists as this operation is irreversible. Approval by default
WriteDelete entity by type and idCall to permanently and irreversibly hard-delete an existing entity (user, agent, app, or run) and all its associated data, using its type and ID. Approval by default
WriteDelete memoriesDeletes all memories matching specified filter criteria. Approval by default
WriteDelete memory batch with uuidsDeletes a batch of up to 1000 existing memories, identified by their UUIDs, in a single API call. Approval by default
WriteDelete projectPermanently deletes a specific project and all its associated data from an organization; this action cannot be undone and requires the project to exist within the specified organization. Approval by default
WriteDelete project memberRemoves an existing member, specified by email address, from a project, immediately revoking their project-specific access; the user is not removed from the organization. Approval by default
WriteDelete webhookDeletes a webhook and stops receiving notifications for the specified webhook ID. Approval by default
WriteRemove a member from the organizationRemoves a member, specified by their username, from an existing organization of which they are currently a member. Approval by default
WriteUpdate memory batch with uuidUpdates text for up to 1000 memories in a single batch, using their UUIDs. Approval by default
WriteUpdate memory text contentUpdates the text content of an existing memory, identified by its `memory_id`. Approval by default
WriteUpdate organization member roleUpdates the role of an existing member to a new valid role within an existing organization. Approval by default
WriteUpdate projectUpdates a project by `project_id` within an `org_id`, modifying only provided fields (name, description, custom_instructions, custom_categories); list fields are fully replaced (cleared by `[]`)… Approval by default
WriteUpdate project member roleUpdates the role of a specific member within a designated project, ensuring the new role is valid and recognized by the system. Approval by default
One prompt, start to finish
What a governed Mem0 run looks like inside Luumen.
Questions
How does LuumenAI connect to Mem0?
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Can LuumenAI change things in Mem0 on its own?
Read actions answer immediately. Anything that writes — add member to project, add new memory records, add organization member, create a new agent, and more — is shown as a plan and requires approval by default, including the 9 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
Who gets access to the integration?
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.
Is there an audit trail?
Every call to Mem0 — 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.