Supermemory MCP integration for AI agents.
Connect AI agents to Supermemory through 8 structured actions, including get document, add document, delete document, and forget memory. Review authenticatio…
- ACTION CONTRACTS
- 8
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Supermemory integration exposes
The Supermemory Agent App exposes 8 provider-backed actions for ai and data work. Its current contract lets an authorized agent get a supermemory document and its current processing status, including the final extracted content when available, submit raw text, a transcript, or a public url for asynchronous memory extraction or managed rag indexing, and permanently delete one source document by its supermemory id or caller-provided custom id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Supermemory account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Supermemory capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_documentREADGet a Supermemory document and its current processing status, including the final extracted content when available.
INPUTS: id
add_documentWRITESubmit raw text, a transcript, or a public URL for asynchronous memory extraction or managed RAG indexing.
INPUTS: content / containerTag / taskType / customId / metadata
delete_documentHIGH IMPACTPermanently delete one source document by its Supermemory ID or caller-provided custom ID.
INPUTS: id
forget_memoryREVIEWSoft-delete one memory by ID so it is excluded from normal recall while remaining auditable.
INPUTS: memoryId / containerTag / reason
create_memoriesWRITEStore one or more already-known facts directly as immediately searchable Supermemory memories.
INPUTS: memories / containerTag
get_profileREADRetrieve long-term, recent, and bucketed profile context for one user or tenant container.
INPUTS: containerTag / q / threshold / filters / include
searchREADRecall relevant memories, document chunks, or both for a question within one tenant container.
INPUTS: q / containerTag / searchMode / limit / threshold
update_memoryWRITECorrect one memory by ID, creating a new version while preserving its prior version history.
INPUTS: memoryId / containerTag / newContent / metadata / forgetAfter
INPUT CONTRACTS
Know what the action needs before it runs.
get_document
idREQUIRED- The Supermemory document identifier.
add_document
contentREQUIRED- Raw text, a conversation transcript, or a public URL that Supermemory should process.
containerTagREQUIRED- The user, project, or tenant container tag that scopes this operation.
taskTypeREQUIRED- How Supermemory should process the content.
customIdOPTIONAL- A stable caller-provided identifier used for idempotency and deletion.
metadataOPTIONAL- Flat metadata used to organize and filter Supermemory content.
delete_document
idREQUIRED- The Supermemory document ID or caller-provided custom ID.
forget_memory
memoryIdREQUIRED- The identifier of the memory to forget.
containerTagREQUIRED- The user, project, or tenant container tag that scopes this operation.
reasonOPTIONAL- Why this memory is being forgotten.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Document
Get a Supermemory document and its current processing status, including the final extracted content when available. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_documentControl Add Document
Submit raw text, a transcript, or a public URL for asynchronous memory extraction or managed RAG indexing. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_documentVerify with Get Profile
Retrieve long-term, recent, and bucketed profile context for one user or tenant container. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_profileSAFETY BOUNDARY
Operate Supermemory with explicit limits
- Authorize Supermemory with API key and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_document` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Supermemory rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Supermemory task completed successfully.
CONNECTION MODEL
API key
Supermemory API key sent as a Bearer token. Create one at https://console.supermemory.ai.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Supermemory.