Agent memory with git-like version control. Custom LLMs turn conversations into structured facts with automatic conflict detection - your agent sees
Agent memory with git-like version control. Custom LLMs turn conversations into structured facts with automatic conflict detection - your agent sees how decisions
Other memory systems dump everything into your context window and hope for the best. Memstate gives your agent a structured, versioned knowledge base it navigates precisely — load only what you need, know what changed, know when facts conflict.
memstate_remember — Store markdown, task summaries, decisions. Server extracts keypaths and detects conflicts automatically. Use for most writes.memstate_set — Set a single keypath to a short value (e.g. config.port = 8080). Not for prose.memstate_get — Browse all memories for a project or subtree. Use at the start of every task.memstate_search — Semantic search by meaning when you don't know the exact keypath.memstate_history — See how a piece of knowledge changed over time — full version chain.memstate_delete — Soft-delete a keypath. Creates a tombstone; full history is preserved.memstate_delete_project — Soft-delete an entire project and all its memories.Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| memstate_remember | markdown summaries, decisions, task results (preferred) |
| memstate_set | single short values only (config flags, status) |
| memstate_get | browse/retrieve before tasks |
| memstate_search | semantic lookup when keypath unknown |
| memstate_history | audit how knowledge evolved |
| memstate_delete | remove outdated memories (history preserved) |
{
"mcpServers": {
"memstate": {
"command": "npx",
"args": [
"-y",
"@memstate/mcp"
],
"env": {
"MEMSTATE_API_KEY": "YOUR_MEMSTATE_API_KEY"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| MEMSTATE_API_KEY | Declared in the maintainer’s client configuration. | Yes |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.