hindsight
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
muse-hindsight-connector
Native Muse Code plugin for long-term
Hindsight memory. One bank per repo
(coding-agent::<project>), shared across agents — what you tell Muse is there
when you open another Hindsight-wired agent.
Works on macOS, Linux, and Windows. Pure Node.js standard library, zero dependencies, no native modules, no subprocesses.
What you get
Capability | How |
| Ensures the repo bank exists, seeds session context |
| Recalls relevant memories into each turn |
| Writes new transcript turns back (incremental cursor, no dupes) |
MCP server |
|
Skill | Companion skill teaching the memory workflow |
Command | One-shot memory status report |
All hooks fail open: if the server is unreachable they output {} and the
session continues untouched.
Related MCP server: engram
Requirements
Node.js ≥ 18 on
PATHA Hindsight server (local default
http://localhost:8888, self-hosted, or Cloud)
Install
git clone https://github.com/aminamos/muse-hindsight-connector.git
muse plugins install ./muse-hindsight-connector
muse plugins approve hindsight-museThen point it at your server (or skip this if you already use Hindsight with Claude Code / Codex — their endpoint is adopted automatically):
node muse-hindsight-connector/bin/cli.js configure
# or with env vars (sh):
# HINDSIGHT_API_URL=http://localhost:8888 HINDSIGHT_API_KEY=<token>
# PowerShell:
# $env:HINDSIGHT_API_URL='http://localhost:8888'; $env:HINDSIGHT_API_KEY='<token>'Verify:
node muse-hindsight-connector/bin/cli.js doctorConfiguration
Endpoint precedence:
HINDSIGHT_API_URL/HINDSIGHT_API_KEYenv vars~/.hindsight/muse.json({apiUrl, apiToken, bankIdTemplate})Adopted
~/.hindsight/claude-code.json/codex.jsonDefault:
http://localhost:8888, no token
Optional overrides: HINDSIGHT_BANK_TEMPLATE (default
coding-agent::{gitProject}), HINDSIGHT_BANK_ID (MCP server only).
Bank naming needs no git binary: the repo name is read from .git/config
purely via the filesystem, falling back to the directory name.
One shared bank across all agents
By default every repo gets its own coding-agent::<project> bank. To share one
bank with other harnesses (e.g. omp's omp bank), set the template to a fixed
name — memories are still tagged per project (project:<name>) and per harness
(harness:muse), so recall stays scoped but nothing is siloed:
node bin/cli.js configure # set bankIdTemplate to: ompTests
npm test # hermetic: stub-server unit + hook + MCP + manifest tests
npm run smoke # live: needs HINDSIGHT_LIVE=1 + HINDSIGHT_SMOKE_BANK=<bank>CI runs npm test on ubuntu / windows / macos × node 18 / 20 / 24.
Hook protocol notes
Muse hooks receive JSON on stdin
(hook_event_name, session_id, cwd, transcript_path, …) and inject
context by printing
{"hookSpecificOutput": {"hookEventName": "<event>", "additionalContext": "…"}}.
The UserPromptSubmit prompt field is read defensively from several candidate
keys. Test one hook directly:
# sh / bash / zsh:
echo '{"hook_event_name":"UserPromptSubmit","cwd":".","prompt":"hi"}' \
| node hooks/user-prompt-submit.js
# PowerShell:
# '{"hook_event_name":"UserPromptSubmit","cwd":".","prompt":"hi"}' | node hooks/user-prompt-submit.jsLicense
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Private memory for AI agents: save and recall facts across Claude Code, Codex, Cursor and ChatGPT.
Shared memory for coding agents. Stop re-explaining your codebase every session.
Persistent cross-session memory shared by Codex, Claude Code, ChatGPT, and other AI agents.
Persistent engineering memory designed to follow developers across coding agents.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables infinite searchable memory for coding agents across sessions, allowing them to recall past decisions and context.60 npm16MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to store, recall, and manage persistent memory across sessions through MCP tools, with reviewable handoffs and SQLite-backed local storage.1MIT
- AlicenseNot gradedqualityBmaintenanceProvides persistent cognitive memory for AI coding agents, enabling them to recall architecture decisions, coding preferences, and project facts across sessions.66MIT
- AlicenseNot gradedqualityFmaintenanceEnables coding agents to store, retrieve, and share durable memories across projects and machines via MCP, with session-start recall and scoped, versioned storage.6MIT