@echomem/mcp 1.4.18 → 1.4.20

package/dist/v1-contract.js

@@ -108,7 +108,7 @@ export function listToolSpecs(opts = {}) {
     const currentTime = new Date().toISOString();
     const map = opts.map?.trim();
     const updateNotice = opts.updateNotice?.trim();
-    const paidRecallNote = "Requires Echo Pro or Power; saving conversations and memory extraction remain included.";
+    const recallPlanNote = "Available on every plan: Free includes 10 searches each week, Pro includes 100, and Power includes 250.";
     const searchBillingReplyInstruction = "If search returns an ACTION REQUIRED subscription message, tell the user to start their trial or subscription and include the exact URL from that result verbatim. Do not respond only with \"connect\" or \"upgrade\".";
     const updateSection = updateNotice ? `\n\nUPDATE NOTICE: ${updateNotice}` : "";
     const mapSection = map
@@ -117,7 +117,7 @@ export function listToolSpecs(opts = {}) {
     return [
         {
             name: canonicalToolNames.search,
-            description: withMcpVersion(`Recall the user's prior decisions, preferences, and project context from EchoMem — their long-term memory across ALL their AI tools, not just this session. Use it instead of re-deriving or re-asking what the user already settled. ${paidRecallNote} ${searchBillingReplyInstruction}${mapSection}\nReturns the ranked memories; set includeAnswer=true only if you need the legacy synthesized answer. Current time: ${currentTime}.${updateSection}`),
+            description: withMcpVersion(`Recall the user's prior decisions, preferences, and project context from EchoMem — their long-term memory across ALL their AI tools, not just this session. Use it instead of re-deriving or re-asking what the user already settled. ${recallPlanNote} ${searchBillingReplyInstruction}${mapSection}\nReturns the ranked memories; set includeAnswer=true only if you need the legacy synthesized answer. Current time: ${currentTime}.${updateSection}`),
             inputSchema: {
                 type: "object",
                 properties: {
@@ -140,7 +140,7 @@ export function listToolSpecs(opts = {}) {
         },
         {
             name: "search_memories_by_description_semantic",
-            description: `Legacy alias for search_memories. ${paidRecallNote} ${searchBillingReplyInstruction}`,
+            description: `Legacy alias for search_memories. ${recallPlanNote} ${searchBillingReplyInstruction}`,
             inputSchema: {
                 type: "object",
                 properties: {
@@ -163,7 +163,7 @@ export function listToolSpecs(opts = {}) {
         },
         {
             name: canonicalToolNames.save,
-            description: "Save this conversation into EchoMem as long-term memory (durable memories are extracted automatically). Saving is included. passthrough=true stores the text verbatim as a session capsule; reloading/searching saved memories requires Echo Pro or Power.",
+            description: "Save this conversation into EchoMem as long-term memory (durable memories are extracted automatically). New extraction input uses the plan's weekly processing allowance; if the limit is reached, nothing is saved. passthrough=true stores the text verbatim as a session capsule.",
             inputSchema: {
                 type: "object",
                 properties: {
@@ -196,7 +196,7 @@ export function listToolSpecs(opts = {}) {
         },
         {
             name: canonicalToolNames.timeRange,
-            description: `Retrieve memories within a specific date range. ${paidRecallNote} Current time: ${currentTime}.`,
+            description: `Retrieve memories within a specific date range. ${recallPlanNote} Current time: ${currentTime}.`,
             inputSchema: {
                 type: "object",
                 properties: {
@@ -214,7 +214,7 @@ export function listToolSpecs(opts = {}) {
         },
         {
             name: canonicalToolNames.keywords,
-            description: `Search memories based on keywords in keys field. ${paidRecallNote}`,
+            description: `Search memories based on keywords in keys field. ${recallPlanNote}`,
             inputSchema: {
                 type: "object",
                 properties: {
@@ -371,7 +371,7 @@ export function listToolSpecs(opts = {}) {
         },
         {
             name: canonicalToolNames.getByContext,
-            description: withMcpVersion(`Deterministically re-fetch the exact batch of memories saved under one contextId — no semantic search, no ranking, just that session's saved capsule. ${paidRecallNote} save_conversation returns a contextId; pass it here to pull back precisely those memories, e.g. to warm up a fresh session with what a prior session saved, or to verify the saved facts are still present. Current time: ${currentTime}.`),
+            description: withMcpVersion(`Deterministically re-fetch the exact batch of memories saved under one contextId — no semantic search, no ranking, just that session's saved capsule. ${recallPlanNote} save_conversation returns a contextId; pass it here to pull back precisely those memories, e.g. to warm up a fresh session with what a prior session saved, or to verify the saved facts are still present. Current time: ${currentTime}.`),
             inputSchema: {
                 type: "object",
                 properties: {
@@ -388,7 +388,7 @@ export function listToolSpecs(opts = {}) {
         },
         {
             name: canonicalToolNames.checkpointByContext,
-            description: withMcpVersion(`Rebuild a clean-context checkpoint / decision log from one EchoMem contextId. ${paidRecallNote} Use this when the user or EchoMem HUD gives you a contextId for a renewed coding session and you need the session handoff, not a raw memory dump. It deterministically fetches that context and formats it as orientation state: decisions, carryover, constraints, and checkpoints. Current time: ${currentTime}.`),
+            description: withMcpVersion(`Rebuild a clean-context checkpoint / decision log from one EchoMem contextId. ${recallPlanNote} Use this when the user or EchoMem HUD gives you a contextId for a renewed coding session and you need the session handoff, not a raw memory dump. It deterministically fetches that context and formats it as orientation state: decisions, carryover, constraints, and checkpoints. Current time: ${currentTime}.`),
             inputSchema: {
                 type: "object",
                 properties: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@echomem/mcp",
-  "version": "1.4.18",
+  "version": "1.4.20",
   "description": "EchoMem MCP bridge: cloud-first memory tools, local context HUD, and the Agent Doctor workspace forensics report (cost ledger + 3D repo city)",
   "main": "dist/index.js",
   "type": "module",

package/templates/codex-skills/echomem-forget/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: echomem-forget
+description: Find, review, and delete outdated or incorrect memories from EchoMem. Use when the user asks EchoMem to forget, remove, or correct remembered information, or says a stored fact is no longer true. Require an explicit confirmation before the destructive delete step and do not operate on another memory provider unless requested.
+---
+
+# EchoMem Forget
+
+Use EchoMem's two-step deletion workflow.
+
+1. Search EchoMem when needed to identify the exact memory and its ID.
+2. Call `delete_memory` with the memory ID only to preview the target and receive a confirmation token.
+3. Show the preview and ask the user to confirm deletion of that exact memory.
+4. Only after confirmation, call `delete_memory` with `confirmed: true` and the exact token.
+5. If the user supplied corrected information, offer to save the replacement with `save_conversation` after deletion.
+
+Never bypass the preview or confirmation step.

package/templates/codex-skills/echomem-forget/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "EchoMem Forget"
+  short_description: "Review and delete an EchoMem memory"
+  default_prompt: "Use $echomem-forget to find the outdated memory, show me what will be deleted, and ask for confirmation."
+policy:
+  allow_implicit_invocation: true

package/templates/codex-skills/echomem-login/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: echomem-login
+description: Connect, authenticate, diagnose, or unlock the local EchoMem MCP bridge. Use when EchoMem reports a missing token, locked or expired encryption key, disconnected MCP server, setup problem, or when the user asks to log in, connect a device, check EchoMem status, or unlock their memory vault.
+---
+
+# EchoMem Login
+
+Use the installed EchoMem CLI and keep credentials out of chat and client configuration.
+
+- Run `echomem-mcp status` to diagnose the current connection.
+- Run `echomem-mcp login` to connect the device through the browser approval flow.
+- EchoMem treats the MCP bridge as a trusted device. A verified local key stays available until the
+  user runs `echomem-mcp lock`, logs out, or removes the local credentials. When the key is absent,
+  tell the user to open their own Terminal and run `echomem-mcp unlock`.
+- Run `echomem-mcp setup --client codex --skip-login` when the MCP entry itself is missing.
+
+Do not run the bare interactive `echomem-mcp unlock` command through an agent shell: it waits for a
+private passphrase that the user must enter themselves. Tell the user that the prompt reads
+`Vault passphrase (typing is hidden):`, no characters appear while typing, and they should press
+Return when finished. After it succeeds, retry the MCP action in the current session; no editor
+restart is needed.
+
+Use `echomem-mcp lock` when the user wants to remove the local vault key without disconnecting their
+device login.
+
+Prefer the interactive browser flow for login. Never print, log, or ask the user to paste tokens,
+passphrases, or encryption keys into the conversation or expose them through command-line flags.

package/templates/codex-skills/echomem-login/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "EchoMem Login"
+  short_description: "Connect or unlock EchoMem locally"
+  default_prompt: "Use $echomem-login to connect this device to EchoMem or unlock my encrypted memory vault."
+policy:
+  allow_implicit_invocation: true

package/templates/codex-skills/echomem-save/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: echomem-save
+description: Save durable knowledge to EchoMem, the user's cross-agent long-term memory. Use when the user asks to remember, save, preserve, or carry forward information, or when active EchoMem guidance requires capturing a meaningful decision, resolved bug, architectural choice, preference, or project milestone. Prefer EchoMem when it is connected; do not silently save to another memory provider.
+---
+
+# EchoMem Save
+
+Use the `save_conversation` tool from the `echomem` MCP server.
+
+1. Capture the goal, decision or outcome, important reasoning, and relevant files or constraints. Omit noise and unrelated transcript content.
+2. Prefer structured `messages`; add a concise title, source, and useful tags.
+3. Use `passthrough: true` only when the user explicitly needs a verbatim session capsule.
+4. Never include secrets, credentials, or unnecessary sensitive content.
+5. Confirm what EchoMem saved. If saving fails, report the failure without switching providers silently.

package/templates/codex-skills/echomem-save/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "EchoMem Save"
+  short_description: "Save durable project knowledge to EchoMem"
+  default_prompt: "Use $echomem-save to preserve this decision and its important context in EchoMem."
+policy:
+  allow_implicit_invocation: true

package/templates/codex-skills/echomem-search/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: echomem-search
+description: Search EchoMem, the user's cross-agent long-term memory, for prior decisions, preferences, project context, and past work. Use when a request refers to previous work or sessions, asks what was decided or how something was implemented, needs a catch-up, or plausibly depends on context the user settled before. Prefer EchoMem when it is connected; do not silently substitute another memory provider.
+---
+
+# EchoMem Search
+
+Use the `echomem` MCP server as the source of long-term memory.
+
+1. Call `search_memories` with a concise query describing the context needed. Keep `includeAnswer` false unless an EchoMem-generated synthesis is specifically useful.
+2. Use `get_memories_by_time_range` for explicit dates, `search_memories_by_keywords` for exact terms, and `get_checkpoint_by_context` when a carryover references an EchoMem checkpoint.
+3. Distinguish recalled facts from inference and preserve dates or provenance returned by EchoMem.
+4. If EchoMem returns an action-required URL, give the user that exact URL and explanation.
+5. If EchoMem is unavailable, say so. Do not switch to another memory provider unless the user requests it.

package/templates/codex-skills/echomem-search/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "EchoMem Search"
+  short_description: "Recall decisions and context from EchoMem"
+  default_prompt: "Use $echomem-search to recall my prior decisions and relevant project context before continuing."
+policy:
+  allow_implicit_invocation: true