Memory with OHarness
- Connecteur
- Serveurs locaux
A knowledge graph the agent can write to and read back in later sessions. OHarness works with Memory out of the box.
Cette page est rédigée en anglais. Les termes qu'elle explique sont ceux que l'on cherche en anglais, et un terme technique traduit est un terme différent.
What you get
| MCP connector | Runs locally as npx -y @modelcontextprotocol/server-memory. |
| Published by | Model Context Protocol |
How it signs in
It does not. The server starts on your machine when a session needs it, through npx, which runs on the Node that OHarness already has. There is no account to create and no key to set.
Try it
Once Memory is connected, a first prompt to see it work:
Use the Memory server to help with this project, and show me each call you make.
Adding it
- Download OHarness for the Mac, or install the CLI anywhere Node runs.
- In the composer, open the + menu and find Memory under Connectors.
- Pick it. The server starts and its tools are available from the next turn.
Links
Common questions
Does OHarness work with Memory?
Yes. Memory ships in OHarness as an MCP connector, so it is in the menu on first launch with nothing to look up.
How does the Memory connector sign in?
It does not need to. It runs as a process on your machine (npx), with nothing to sign in to.
Is OHarness affiliated with Model Context Protocol?
No. OHarness works with Memory through its public MCP server; Memory and its logo belong to Model Context Protocol.
More in local servers
Everything · Fetch · Filesystem · Git · Sequential thinking · Time
Memory and its logo belong to Model Context Protocol. Listed because OHarness works with it, not because Model Context Protocol endorses OHarness.
Use Memory from OHarness
The same Memory tools in every session, whichever of the model providers is underneath.