health.pingLABSCO SUMMARY
Access control is the part most memory servers leave out.
A space carries an ACL with reader, writer and admin roles and a TTL on both the space and each individual grant, so a second agent can be given read access to one slice of memory that expires by itself. The short-term buffer is the other useful seam: a session's scratch notes stay out of the vector store until you flush them.
What it is
A Go MCP server providing vector-native memory: a short-term buffer per session, long-term embedded storage, and shared "spaces" that several agents or users can read and write under access control.
What you get
- Core memory —
memory.add_shortbuffers within a session,memory.flushcommits the buffer to long-term storage,memory.store_longwrites straight through,memory.retrieve_contextpulls back what's relevant to a query memory.embedreturns the vector for a piece of text on its own- Shared spaces —
spaces.upsert,spaces.grant,spaces.revoke,spaces.list, withreader,writerandadminroles and a time-to-live on both grants and spaces - Session sharing —
shared.join,shared.leave,shared.add_short_toandshared.retrievefor a merged view of local memory plus joined spaces health.pingfor liveness andengine.metricsfor a performance snapshot- Four storage backends: in-memory, PostgreSQL with pgvector, Qdrant, or MongoDB Atlas Vector Search
Requirements
go install github.com/Protocol-Lattice/memory-bank-mcp@latest, then run memory-bank-mcp — stdio by default, or -transport http -addr :8080. Choose a backend with MEMORY_STORE and give it connection settings: POSTGRES_DSN, QDRANT_URL with QDRANT_COLLECTION, or MONGO_URI with database and collection. The embedding model comes from the ADK_EMBED_PROVIDER and ADK_EMBED_MODEL variables plus that provider's key. SHORT_TERM_SIZE defaults to 20 and DEFAULT_SPACE_TTL_SEC to 86400.
Setup effort
One command — go install github.com/Protocol-Lattice/memory-bank-mcp@latest
USE CASES
01
Keeping decisions across sessions
Store what was agreed in long-term memory and retrieve the relevant pieces when the next session opens.
02
Letting scratch notes settle before they're permanent
Buffer observations during the session and commit them only when the work turns out to be worth keeping.
03
Sharing context between two agents
Create a space, grant one agent writer and the other reader, and let both retrieve from a merged view.
04
Giving temporary access that cleans itself up
Attach a TTL to the grant so it lapses without anyone remembering to revoke it.
15 tools
Listed in project docs. Your client may show a different list.
memory.embedmemory.add_shortmemory.flushmemory.store_longmemory.retrieve_contextspaces.upsertspaces.grantspaces.revokespaces.listshared.joinshared.leaveshared.add_short_toshared.retrieveengine.metricsBEFORE YOU INSTALL
What to know first
Tools you get
15 tools named in the project's documentation.
Requires
memory-bank-mcp on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
go install github.com/Protocol-Lattice/memory-bank-mcp@latestMCP Clients
VS Code
VS CODE · JSON
{
"servers": {
"memory-bank": {
"command": "memory-bank-mcp"
}
},
"inputs": []
}This is the project's block, in VS Code's mcp.json format (servers + inputs). memory-bank-mcp must be on your PATH, which is where go install puts it if your Go bin directory is on PATH.
