From 570a0a593260812102d747127f68a3ff1d1737ea Mon Sep 17 00:00:00 2001
From: MaheshtheDev <38828053+MaheshtheDev@users.noreply.github.com>
Date: Fri, 6 Nov 2026 16:32:00 +0000
Subject: [PATCH] docs(claude-code): MCP tools follow Claude Code permission
 rules

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---
 apps/docs/integrations/claude-code.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/docs/integrations/claude-code.mdx b/apps/docs/integrations/claude-code.mdx
index 1bce1aac..aaf401a9 100644
--- a/apps/docs/integrations/claude-code.mdx
+++ b/apps/docs/integrations/claude-code.mdx
@@ -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