Supermemory
Supermemory is a memory and context API for ingesting, organizing, searching, and recalling information across applications.
Integration
- Vendor
- Supermemory
- Category
- other
- Auth
- API_KEY
- Tools
- 11
- Composio slug
supermemory
Tools
- Add Document
Ingest text or a public URL as a Supermemory document and return its document ID and initial processing status.
- Add Documents
Add 1 to 600 documents in one request, with explicit per-document metadata and processing options. HTTP 200 may contain partial failures; callers must inspect failed, success, and every result rather than treating 200 as complete batch succ
- Delete Documentdestructive
Permanently delete one document by ID. This does not remove the document's container-tag settings record.
- Get Account Status
Return the connected Supermemory organization's plan, credit balance, high-level usage, and reset date.
- Get Document
Get one document's content, metadata, source details, and processing status by document ID.
- Get Document Chunks
Return the ordered extracted chunks for one processed document.
- Get Profile
Retrieve the static, dynamic, or bucketed profile learned for one container tag, optionally with matching search results.
- List Documents
List documents, optionally filtered by containers, metadata, or filepath, one page at a time.
- List Memories
List extracted memory entries for one or more container tags, one page at a time.
- Search Memory
Semantically search Supermemory memories, document chunks, or both, with optional container and metadata filters.
- Update Document
Update the content, metadata, container, or processing configuration of one existing document. When metadata is supplied, it completely replaces the document's metadata, so omitted metadata keys are removed.
Setup
- Create or open a Switchy Project.
- Open Integrations and connect Supermemory.
- Authorise through api_key. Switchy stores the connection against your org.
- Everyone in the Project can now @-mention the Supermemory tools in chat.
What teammates see: by default, memories from Supermemory are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.