Skip to content

docs: add Engram MCP memory server integration guide#2345

Open
manaporkun wants to merge 2 commits intosipeed:mainfrom
manaporkun:docs/engram-mcp-memory
Open

docs: add Engram MCP memory server integration guide#2345
manaporkun wants to merge 2 commits intosipeed:mainfrom
manaporkun:docs/engram-mcp-memory

Conversation

@manaporkun
Copy link
Copy Markdown
Contributor

Summary

  • Adds documentation for connecting Engram as an MCP server for persistent, searchable memory
  • Includes install instructions (Homebrew and Go) and a ready-to-use config.json example
  • Tested on Pi Zero 2 W running PicoClaw + Engram as a personal AI advisor

Test plan

  • Verify the new section renders correctly in the GitHub markdown preview
  • Confirm the config.json snippet is valid JSON
  • Test the Engram install commands on a fresh environment

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings April 4, 2026 23:36
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds a new documentation section describing how to run the Engram MCP server alongside PicoClaw to provide persistent, searchable memory, including install commands and a config.json example.

Changes:

  • Document Engram as an MCP server option for persistent memory.
  • Add install instructions (Homebrew + go install).
  • Provide a ready-to-use MCP server configuration snippet for config.json.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +480 to +484
"engram": {
"enabled": true,
"command": "engram",
"args": ["mcp", "--tools=agent", "--project=my-assistant"]
}
Copy link

Copilot AI Apr 4, 2026

Choose a reason for hiding this comment

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

The example uses --project=my-assistant without indicating it’s a placeholder. To avoid users accidentally sharing/overwriting the same Engram project across environments, consider using a clearer placeholder (e.g., YOUR_PROJECT_NAME) and/or adding a short note that this value should be customized per assistant/user.

Copilot uses AI. Check for mistakes.
}
```

This gives your agent 11 memory tools including `mem_save`, `mem_search`, `mem_context`, and `mem_session_summary`. See the [Engram documentation](https://github.com/Gentleman-Programming/engram) for the full tool reference.
Copy link

Copilot AI Apr 4, 2026

Choose a reason for hiding this comment

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

This sentence hard-codes both the exact number of tools ("11") and specific tool names. Since these can change between Engram versions and also depend on the selected --tools= set, consider removing the exact count and phrasing it more defensively (e.g., “provides memory tools such as …”) while keeping the link to Engram’s tool reference.

Suggested change
This gives your agent 11 memory tools including `mem_save`, `mem_search`, `mem_context`, and `mem_session_summary`. See the [Engram documentation](https://github.com/Gentleman-Programming/engram) for the full tool reference.
This provides your agent with Engram memory tools such as `mem_save`, `mem_search`, `mem_context`, and `mem_session_summary`. See the [Engram documentation](https://github.com/Gentleman-Programming/engram) for the full tool reference.

Copilot uses AI. Check for mistakes.
@sipeed-bot sipeed-bot bot added type: documentation Improvements or additions to documentation domain: tool labels Apr 4, 2026
…ol count

Address review feedback:
- Change --project=my-assistant to --project=<your-project> with a note to customize
- Replace "11 memory tools including" with "memory tools such as" to avoid staleness

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

domain: tool type: documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants