@echomem/mcp 1.4.23 → 1.4.24

package/dist/index.js

@@ -4,7 +4,7 @@ import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js"
 import { CallToolRequestSchema, ErrorCode, ListToolsRequestSchema, McpError, } from "@modelcontextprotocol/sdk/types.js";
 import axios from "axios";
 import { ZodError } from "zod";
-import { canonicalToolNames, completeGroupPublicationSchema, createGroupInviteSchema, createGroupSchema, deleteMemorySchema, getByContextSchema, groupContextSchema, joinGroupSchema, keywordsSchema, listFriendsSchema, listToolSpecs, othersSchema, publishBatchToGroupSchema, publishToGroupSchema, prepareGroupPublicationSchema, publicMemorySchema, resolveCanonicalToolName, saveConversationSchema, searchMemoriesSchema, searchUsersSchema, sendFriendRequestSchema, timeRangeSchema, } from "./v1-contract.js";
+import { canonicalToolNames, completeGroupPublicationSchema, createGroupInviteSchema, createGroupSchema, deleteMemorySchema, getByContextSchema, groupContextSchema, joinGroupSchema, keywordsSchema, listFriendsSchema, listToolSpecs, othersSchema, publishBatchToGroupSchema, publishToGroupSchema, prepareGroupPublicationSchema, publicMemorySchema, resolveCanonicalToolName, saveConversationSchema, searchMemoriesSchema, searchUsersSchema, sendFriendRequestSchema, timeRangeSchema, updateGroupProfileSchema, } from "./v1-contract.js";
 import { KeyStore } from "./keystore.js";
 import { EventLogger, hashText } from "./events.js";
 import { buildReportText } from "./report.js";
@@ -983,6 +983,11 @@ class EchoMemApiClient {
         const response = await this.axios.post("/api/extension/social/groups/current/publications/prepare", parsed, { headers: enc.enabled && enc.key ? { "X-Encryption-Key": enc.key } : undefined });
         return response.data;
     }
+    async updateGroupProfile(args) {
+        const parsed = updateGroupProfileSchema.parse(args ?? {});
+        const response = await this.axios.patch("/api/extension/social/groups/current/profile", parsed);
+        return response.data;
+    }
     async completeGroupPublication(args) {
         const parsed = completeGroupPublicationSchema.parse(args ?? {});
         const enc = await this.encState();
@@ -1205,6 +1210,8 @@ class EchoMemMCPServer {
                         return await this.handleJoinGroup(request.params.arguments);
                     case canonicalToolNames.prepareGroupPublication:
                         return await this.handlePrepareGroupPublication(request.params.arguments);
+                    case canonicalToolNames.updateGroupProfile:
+                        return await this.handleUpdateGroupProfile(request.params.arguments);
                     case canonicalToolNames.completeGroupPublication:
                         return await this.handleCompleteGroupPublication(request.params.arguments);
                     case canonicalToolNames.publishToGroup:
@@ -1776,6 +1783,9 @@ Details: ${m.details || "N/A"}`;
         const participants = Array.isArray(payload?.participants)
             ? payload.participants.filter(isRecord)
             : [];
+        const currentParticipant = isRecord(payload?.currentParticipant)
+            ? payload.currentParticipant
+            : null;
         const coverage = isRecord(payload?.coverage) ? payload.coverage : {};
         if (!group) {
             return {
@@ -1803,6 +1813,10 @@ Details: ${m.details || "N/A"}`;
             participantText,
             "",
             "Declared titles and responsibilities are directory facts. Use search_others_memories for current work evidence, and label suggested contribution areas as inference that should be confirmed with the team.",
+            currentParticipant
+                && (!readString(currentParticipant, "title") || !readString(currentParticipant, "responsibilitySummary"))
+                ? "Your group profile is incomplete. Use prepare_group_publication to review your memory evidence, propose the missing fields, and save them only after confirmation with update_group_profile."
+                : "",
         ].filter(Boolean).join("\n");
         return { content: [{ type: "text", text }] };
     }
@@ -1854,8 +1868,8 @@ Details: ${m.details || "N/A"}`;
             content: [{
                     type: "text",
                     text: payload?.alreadyMember
-                        ? `You are already a member of ${payload?.group?.name ?? "this group"}. No memories were published.`
-                        : `Joined ${payload?.group?.name ?? "the company group"}. No memories were published. Use prepare_group_publication to review candidates.`,
+                        ? `You are already a member of ${payload?.group?.name ?? "this group"}. No memories were published. Use prepare_group_publication to review memories and propose any missing title or responsibility fields.`
+                        : `Joined ${payload?.group?.name ?? "the company group"}. No memories were published. Next use prepare_group_publication to review candidates, infer a proposed title and responsibility summary, and ask the user to confirm that profile together with the publication preview.`,
                 }],
         };
     }
@@ -1863,6 +1877,9 @@ Details: ${m.details || "N/A"}`;
         const parsed = prepareGroupPublicationSchema.parse(args ?? {});
         const payload = await this.client.prepareGroupPublication(parsed);
         const candidates = Array.isArray(payload?.candidates) ? payload.candidates : [];
+        const participantProfile = isRecord(payload?.participantProfile)
+            ? payload.participantProfile
+            : {};
         const formatted = candidates.map((candidate, index) => [
             `[${index + 1}] Memory ID: ${readString(candidate, "memoryId") ?? "unknown"}`,
             `Created: ${readString(candidate, "createdAt") ?? "unknown"}`,
@@ -1879,10 +1896,29 @@ Details: ${m.details || "N/A"}`;
                         `Prepared publication scan ${payload?.scanId} for ${payload?.group?.name ?? "your group"}.`,
                         `Window: ${payload?.windowStart ?? "context start"} → ${payload?.windowEnd}`,
                         `Candidates: ${candidates.length}. Nothing has been published.`,
+                        `Current title: ${readString(participantProfile, "title") ?? "Not declared"}`,
+                        `Current declared responsibility: ${readString(participantProfile, "responsibilitySummary") ?? "Not provided"}`,
                         "",
                         formatted,
                         "",
-                        "Select exact memory IDs matching the user's instruction, show the preview, and ask for confirmation before calling complete_group_publication.",
+                        "Select exact memory IDs matching the user's instruction. From memory evidence, draft a concise title and responsibility summary. Show the profile proposal and memory preview together, then ask for one explicit confirmation. After confirmation, call update_group_profile and complete_group_publication.",
+                    ].join("\n"),
+                }],
+        };
+    }
+    async handleUpdateGroupProfile(args) {
+        const parsed = updateGroupProfileSchema.parse(args ?? {});
+        const payload = await this.client.updateGroupProfile(parsed);
+        const participant = isRecord(payload?.participant) ? payload.participant : {};
+        return {
+            content: [{
+                    type: "text",
+                    text: [
+                        "Confirmed company-group profile updated.",
+                        `Display name: ${readString(participant, "displayName") ?? parsed.displayName ?? "unchanged"}`,
+                        `Title: ${readString(participant, "title") ?? parsed.title}`,
+                        `Declared responsibility: ${readString(participant, "responsibilitySummary") ?? parsed.responsibilitySummary}`,
+                        "These fields are now declared directory facts visible to group members.",
                     ].join("\n"),
                 }],
         };

package/dist/package-metadata.js

@@ -28,8 +28,9 @@ export const MCP_SERVER_INSTRUCTIONS = [
     `If the user or local config expects a newer EchoMem MCP version than ${MCP_PACKAGE_VERSION}, update once with \`${MCP_UPDATE_ALL_COMMAND}\` and start a new MCP session.`,
     "Use echomem_update_status to check whether npm has a newer bridge; it is cached and non-blocking during normal tool listing.",
     "Do not auto-update on every MCP startup; this bridge is intentionally stable between explicit updates.",
-    "For company-group sharing, use get_group_context for orientation; create_memory_group/create_group_invite/join_memory_group for membership; and prepare_group_publication as a no-write preview before complete_group_publication.",
-    "Never complete a group publication without explicit confirmation of the prepared candidate set, and never store or log an echo_grp_ invite code.",
+    "For company-group sharing, use get_group_context for orientation; create_memory_group/create_group_invite/join_memory_group for membership; and prepare_group_publication as a no-publication preview.",
+    "After joining or when profile fields are missing, use candidate memory evidence to propose a title and responsibility summary. Ask the user to confirm that proposal together with the publication preview, then call update_group_profile and complete_group_publication.",
+    "Never save an inferred group profile or complete a group publication without explicit confirmation, and never store or log an echo_grp_ invite code.",
 ].join(" ");
 export function withMcpVersion(description) {
     return `${description}\n\nEchoMem MCP bridge: ${MCP_PACKAGE_LABEL}. If this version is stale, update once with \`${MCP_UPDATE_ALL_COMMAND}\` (or add \`--client cursor|windsurf|claude-desktop|claude-code|codex\` for a single client), then start a new MCP session. Do not run updates repeatedly or on every startup.`;

package/dist/setup.js

@@ -396,10 +396,11 @@ function echomemGuidanceBlock() {
         "- Use `get_group_context` when the user asks who is in their company group, what teammates are responsible for, or what work is already covered. Treat declared participant fields as facts and published-memory conclusions as evidence or inference.",
         "- A group publication is separate from a globally public memory: publishing to a group creates a group-scoped snapshot and must not change the encrypted original or its global `is_public` setting.",
         "- If a user asks to create a group, call `create_memory_group`; if they ask for a code to share, call `create_group_invite` and return the secret invite code only to that user. Never save the invite code to memory or include it in logs, analytics, summaries, or unrelated output.",
-        "- If a user supplies an `echo_grp_...` code and explicitly asks to join, call `join_memory_group`. Joining never authorizes publishing by itself and must not move a user out of another group.",
-        "- For requests such as “prepare my recent work memories,” “upload work from this ticket,” or “publish work since my last sync,” call `prepare_group_publication` first. This is a no-write preview. For encrypted accounts, tell the user to run `echomem-mcp unlock` locally if the tool reports that the key is required.",
-        "- After preparing, select only exact candidate memory IDs that match the user's stated scope, exclude already-published or exact-content duplicates, summarize what would be shared, and ask the user to confirm. Do not call `complete_group_publication` until the user explicitly confirms that preview.",
-        "- On confirmation, call `complete_group_publication` with the exact `scanId`, selected memory IDs, and `confirmed: true`. An explicit request to join and upload still requires the publication preview and confirmation after joining.",
+        "- If a user supplies an `echo_grp_...` code and explicitly asks to join, call `join_memory_group`. Joining never authorizes publishing by itself and must not move a user out of another group. After joining, continue into the profile-and-publication preview instead of leaving title or responsibility blank.",
+        "- For requests such as “prepare my recent work memories,” “upload work from this ticket,” or “publish work since my last sync,” call `prepare_group_publication` first. This is a no-publication preview. For encrypted accounts, tell the user to run `echomem-mcp unlock` locally if the tool reports that the key is required.",
+        "- After preparing, select only exact candidate memory IDs that match the user's stated scope and exclude already-published or exact-content duplicates. Use the candidate evidence to draft a concise title and responsibility summary for the current member, but label both as proposals rather than facts.",
+        "- Present the proposed title/responsibility and the memory publication preview together and ask for one explicit confirmation. Never save an inferred profile or publish memories before confirmation.",
+        "- On confirmation, call `update_group_profile` with the confirmed title, responsibility summary, and `confirmed: true`, then call `complete_group_publication` with the exact `scanId`, selected memory IDs, and `confirmed: true`. If the user edits either proposal, use their wording. An explicit request to join and upload still requires this combined preview and confirmation.",
         "- If the user asks to show, reopen, restart, or bring back the EchoMem HUD (the context-health overlay), run the shell command `echomem-hud app --client auto`.",
         "- If the user wants the HUD to come back after a computer restart, run the shell command `echomem-hud autostart on --client auto`.",
         AGENTS_MD_END,

package/dist/v1-contract.js

@@ -15,6 +15,7 @@ export const canonicalToolNames = {
     createGroupInvite: "create_group_invite",
     joinGroup: "join_memory_group",
     prepareGroupPublication: "prepare_group_publication",
+    updateGroupProfile: "update_group_profile",
     completeGroupPublication: "complete_group_publication",
     publishToGroup: "publish_memory_to_group",
     publishBatchToGroup: "publish_memories_to_group",
@@ -143,6 +144,13 @@ export const prepareGroupPublicationSchema = z.object({
     limit: z.number().int().min(1).max(50).optional(),
     instruction: z.string().max(500).optional(),
 });
+export const updateGroupProfileSchema = z.object({
+    ...triggerMetadataSchema,
+    displayName: z.string().min(1).max(120).optional(),
+    title: z.string().min(1).max(160),
+    responsibilitySummary: z.string().min(1).max(1000),
+    confirmed: z.literal(true),
+});
 export const completeGroupPublicationSchema = z.object({
     ...triggerMetadataSchema,
     scanId: z.string().min(1),
@@ -460,7 +468,7 @@ export function listToolSpecs(opts = {}) {
         },
         {
             name: canonicalToolNames.joinGroup,
-            description: "Join a company memory group using an invite code after the user explicitly asks to join. Joining never publishes memories; call prepare_group_publication separately.",
+            description: "Join a company memory group using an invite code after the user explicitly asks to join. Joining never publishes memories. Next call prepare_group_publication, infer a proposed title and responsibility summary from the user's own candidate memories, and ask the user to confirm the profile together with the publication preview.",
             inputSchema: {
                 type: "object",
                 properties: {
@@ -474,7 +482,7 @@ export function listToolSpecs(opts = {}) {
         },
         {
             name: canonicalToolNames.prepareGroupPublication,
-            description: "Prepare a no-write preview of up to 50 owned memories for group publication. For encrypted accounts the local bridge must be unlocked. The host agent selects exact work-related memory ids from the returned candidates and asks the user to confirm; this tool never publishes.",
+            description: "Prepare a no-publication preview of up to 50 owned memories for group publication. For encrypted accounts the local bridge must be unlocked. The host agent selects exact work-related memory ids, drafts a concise title and responsibility summary from memory evidence, and asks the user to confirm both the profile and publication selection together. This tool never publishes.",
             inputSchema: {
                 type: "object",
                 properties: {
@@ -488,6 +496,20 @@ export function listToolSpecs(opts = {}) {
                 },
             },
         },
+        {
+            name: canonicalToolNames.updateGroupProfile,
+            description: "Save the current member's declared group title and responsibility summary only after the user explicitly confirms the agent's proposal. These become directory facts visible to group members; never save an unconfirmed inference.",
+            inputSchema: {
+                type: "object",
+                properties: {
+                    displayName: { type: "string" },
+                    title: { type: "string" },
+                    responsibilitySummary: { type: "string" },
+                    confirmed: { type: "boolean", const: true },
+                },
+                required: ["title", "responsibilitySummary", "confirmed"],
+            },
+        },
         {
             name: canonicalToolNames.completeGroupPublication,
             description: "Publish only the exact memory ids from a prepared scan after the user explicitly confirms the preview. confirmed must be true. Completing an empty selection safely advances the scan cursor without publishing.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@echomem/mcp",
-  "version": "1.4.23",
+  "version": "1.4.24",
   "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",