Supermemory for AI agents
Supermemory is a memory and context API that lets applications ingest, organize, search, and recall documents and information across sessions. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Supermemory.
Search stored memories
Search across stored memories to find the most relevant document before an agent answers a question.
Add a new document to memory
Add a new document to a user's memory store so future searches can retrieve it.
Delete a document with confirmation
Delete a stored document only after the user confirms it is no longer needed.
11 Supermemory actions, graded by risk.
Every Supermemory action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
7Look things up. Allowed by default.
- supermemory.get_profileGet Profile
- supermemory.get_documentGet Document
- supermemory.list_memoriesList Memories
- supermemory.list_documentsList Documents
- supermemory.search_contextSearch Memory
- supermemory.get_account_statusGet Account Status
- supermemory.get_document_chunksGet Document Chunks
write
3Create and change things. Allow, or ask the user first.
- supermemory.add_documentAdd Document
- supermemory.add_documentsAdd Documents
- supermemory.update_documentUpdate Document
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- supermemory.delete_documentDelete Document
Supermemory in three steps.
- 01Your users connect SupermemoryThey add their Supermemory api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “update Document” can wait for the user, and “delete Document” can be denied outright.
- 03Any agent can actYour agent calls Supermemory through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('supermemory', { read: 'allow', write: 'ask', // update_document destructive: 'deny', // delete_document }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Supermemory connects.
Users add their Supermemory api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Supermemory connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Supermemory from any agent.
Supermemory and Arc0, answered.
Can I use Supermemory with Claude, ChatGPT or Cursor?
Yes. Connect Supermemory to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Supermemory actions you allow.
How do users connect Supermemory?
Users add their Supermemory api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Supermemory actions can my agent take?
11 in total: 7 read, 3 write and 1 destructive, such as “update Document”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Supermemory?
Yes. Actions like “delete Document” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Supermemory too?
Yes. The same Supermemory connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Supermemory into your agent.
Your users connect Supermemory once, under your brand. Your agent gets 11 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan