scriptoriumadmin/supermemory
1
0
Fork 0
mirror of https://github.com/supermemoryai/supermemory.git synced 2026-11-14 09:01:45 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

docs(claude-code): MCP tools follow Claude Code permission rules

Browse source 
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This commit is contained in:
MaheshtheDev 2026-11-06 16:32:00 +00:00
parent a5c3a9fcbc
commit 570a0a5932
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
apps/docs/integrations/claude-code.mdx
View file

@ -75,7 +75,7 @@ Once installed, the plugin runs automatically:
- **Direct recall** — Before Claude sees each substantive prompt, the hook searches Supermemory and injects fresh matches. Set `recallDirective` to switch to advisory mode, where Claude decides when to search.
- **Auto-capture** — After each Claude response (the Stop hook), conversation content added since the last save is captured in the background.
- **Shared repo memory** — Captures go to one repository container shared with the Codex, OpenCode, and Cursor plugins, tagged with `sm_scope: personal` metadata.
- **MCP tools** — The hosted Supermemory MCP tools (`search_memory`, `add_memory`, and more) use the same credentials. `search_memory` and the legacy camelCase read tools (`listMemories`, `listDocuments`, `getDocument`, `listSpaces`, `whoAmI`) are approved automatically; other tools, including `list_memories`, `list_documents`, `get_document` and `get_profile`, still ask for approval. For deeper history, Claude can also use the `context-gatherer` agent.
- **MCP tools** — The hosted Supermemory MCP tools (`search_memory`, `add_memory`, and more) use the same credentials. The plugin doesn't pre-approve any of them, so each tool follows your Claude Code permission rules and asks for approval until you allow it. For deeper history, Claude can also use the `context-gatherer` agent.
## Commands