Skip to content

feat(mcp): productize one-time proactive-memory setup for chat clients - #1352

Open
harrymove-ctrl wants to merge 2 commits into
devfrom
feat/mcp-one-time-proactive-setup
Open

harrymove-ctrl wants to merge 2 commits into
devfrom
feat/mcp-one-time-proactive-setup

Conversation

@harrymove-ctrl

Copy link
Copy Markdown
Collaborator

Summary

Productizes the one-time proactive-memory consent setup for Claude Desktop chat, Claude web, and other chat clients that do not run plugin lifecycle hooks or inject initialize.instructions into the model prompt:

  • Defines the canonical user-pasteable CONSENT_INSTRUCTION and exposes the memwal_enable_proactive MCP prompt (prompts/list and prompts/get) in both @mysten-incubation/memwal-mcp (locally in bridge and auth-required modes) and the relayer MCP sidecar (services/server/scripts/mcp).
  • Updates the /connect/mcp success screen (ConsentSetupCard in apps/app/src/pages/ConnectMcp.tsx) to guide users through the three one-time setup steps: choosing native vs Walrus Memory, pasting CONSENT_INSTRUCTION, and selecting Always allow for memwal_remember and memwal_remember_bulk after the first save.
  • Updates apps/app/public/skills/setup, docs/mcp/claude-desktop.md, docs/mcp/claude-connector.md, and docs/guides/system-prompt-templates.md with the unified one-time setup instructions and adds a sync test (packages/mcp/test/consent-instruction-sync.test.mjs) verifying that all six user-pasteable copies of CONSENT_INSTRUCTION remain byte-equal.

Verification

  • pnpm --filter @mysten-incubation/memwal-mcp test (335/335 passed, including prompts.test.mjs and consent-instruction-sync.test.mjs)
  • cd services/server/scripts && npx tsx --test mcp/__tests__/*.test.ts (243/243 passed, including prompts.test.ts)
  • cd apps/app && npx vitest run src/pages/ConnectMcp.test.tsx src/test/setupSkill.test.ts (9/9 passed)

@harrymove-ctrl
harrymove-ctrl requested a review from ducnmm October 31, 2026 10:20

@ducnmm ducnmm left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new local MCP prompt needs a publishable package version before release. This is a static diff/manifest review; I did not rerun the MCP or app test suites.

return {
protocolVersion,
capabilities: { tools: { listChanged: true } },
capabilities: { tools: { listChanged: true }, prompts: {} },

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P2] Include a release bump for the changed MCP package

This adds a user-visible prompt capability to the distributed CLI, but the PR leaves the MCP package at 0.0.17 while main already publishes 0.0.18. Merging the code onto current dev still leaves the new behavior on the already-published 0.0.18 unless a new version is included, so existing npm users cannot receive this feature through a new package release. Update the tracked MCP manifests/plugin metadata, paired changelogs and release-verifier pin to a version above the published one.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 6d3574b: bumped packages/mcp and all six plugin and marketplace manifests to 0.0.19 with synchronized CHANGELOG entries while preserving mcpBootstrapVersion 0.0.17-dev.3.

@harrymove-ctrl
harrymove-ctrl force-pushed the feat/mcp-one-time-proactive-setup branch from 3b58ebe to 6d3574b Compare October 31, 2026 16:14
@harrymove-ctrl

Copy link
Copy Markdown
Collaborator Author

Rebased onto dev and prepared publishable MCP 0.0.19 release across package.json, marketplace manifests, plugin manifests, and changelogs.

@harrymove-ctrl
harrymove-ctrl requested a review from ducnmm October 31, 2026 16:14

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants