Skip to content

Add opt-in MemPalace MCP setup for Jarvis workflows - #23

Draft
lippytm with Copilot wants to merge 1 commit into
masterfrom
copilot/add-mempalace
Draft

lippytm with Copilot wants to merge 1 commit into
masterfrom
copilot/add-mempalace

Conversation

Copilot AI commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Introduce MemPalace as a local memory layer for Jarvis assistants and swarms, with connection guidance spanning the requested AI, hosting, social, and workflow platforms.

  • MCP configuration

    • Add a disabled-by-default service entry and stdio client template using mempalace-mcp.
    • Document isolated installation and client registration; no hosted API or credentials required.
  • Workflow boundaries

    • Describe ingestion, recall, and assistant handoffs.
    • Distinguish MCP-compatible clients from platforms requiring authorized exports or separate adapters. No live connections or automatic ingestion are provisioned.
  • Privacy safeguards

    • Ignore private memory, imports, and local configuration.
    • Document consent, trust isolation, retention, and approval requirements.
    • Add regression coverage for configuration consistency and private-path exclusions.

Note

Add opt-in MemPalace MCP setup for Jarvis workflows

  • Adds a disabled mempalace entry to services.example.json using stdio transport and the mempalace-mcp command, with no credentials or cloud API fields
  • Adds an MCP client config template in mempalace.mcp.example.json whose command and arguments match the service registry entry
  • Documents MemPalace setup, a mine-and-search check, and privacy safeguards in README.md; the repo does not launch MemPalace or configure platform connectors
  • Ignores .mempalace/, mempalace-data/, memory-imports/, and the local MCP config path in .gitignore
  • Tests in mempalace.test.js verify the opt-in registry entry, template consistency, and Git ignore status

Macroscope summarized b101624.

RetriggerView in GreptileConfidence Score: 5/5

The PR appears safe to merge; no actionable issues were found.

Summary

Adds an opt-in local MemPalace setup for Jarvis workflows.

  • Jarvis assistants can use MemPalace memory through a manually configured MCP client.
  • MemPalace setup keeps imports and platform connections under user control.

No actionable issues were found.

Reviews (1) · Last reviewed commit: "Add opt-in MemPalace MCP setup for Jarvi..." · Reviewed by Greptile

Co-authored-by: lippytm <65956507+lippytm@users.noreply.github.com>
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.

2 participants