feat: add listMemories tool to the Supermemory MCP server#1044
Open
mvanhorn wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Agents can now enumerate stored memories through a new
listMemoriestool on the Supermemory MCP server, returning a page of memory records plus anextCursorfor paging rather than only the top-K of arecallquery.Why this matters
Issue #1030 notes the MCP server in
apps/mcp/src/server.tsonly exposedmemory,recall, andlistProjects, so there was no way to list memories to audit, bulk-clean, or diff them before a save/forget. The newSupermemoryClient.listMemoriesinapps/mcp/src/client.tsacceptscontainerTag,limit,cursor,sort, and a substringfilter, normalizing results the same waysearch()does, and the fourthregisterToolblock inserver.tsmirrors therecallregistration with a Zod schema that clampslimitto 1..200 and validatessort, returning{ memories, nextCursor }scoped by the existingcontainerTagsemantics.Testing
The Zod input schema is exercised at registration: out-of-range
limitand invalidsortare rejected with validation messages before reaching the API, and the empty-store path returns an empty list with a null cursor. Verified by building the MCP package; full suite runs in CI.Fixes #1030