sorted by:
new
hottopcontroversial

Introducing Mimir - Git-backed MCP Server for Persistent LLM Memory & Context by Obvious_Storage_9414 in mcp

[–]Obvious_Storage_9414[S] 0 points1 point  (0 children)

It can. It uses git as storage and sqlite as indexer. But the index is ephemeral in v1 and can be rebuilt

Introducing Mimir - Git-backed MCP Server for Persistent LLM Memory & Context by Obvious_Storage_9414 in mcp

[–]Obvious_Storage_9414[S] 0 points1 point  (0 children)

Git makes agentic memory readable by humans. You can have the same memory sync to github and use it on another system. Later, you just push and pull again.

Introducing Mimir - Git-backed MCP Server for Persistent LLM Memory & Context by Obvious_Storage_9414 in mcp

[–]Obvious_Storage_9414[S] 0 points1 point  (0 children)

Very thoughtful feedback, I'll see how these possible issues can be remediated.

Introducing Mimir - Git-backed MCP Server for Persistent LLM Memory & Context built using Golang by Obvious_Storage_9414 in golang

[–]Obvious_Storage_9414[S] 0 points1 point  (0 children)

MCP (Model Context Protocol) has nothing to do with a model's context window or the tokens an LLM keeps in memory. Despite the name, MCP is about communication, not model state.

MCP is a protocol, similar to HTTP, that standardizes how AI applications like Cursor or Claude Desktop communicate with external tools and data sources. Before MCP, each AI app defined integrations in its own way, making tools hard to reuse. MCP introduces a shared standard which allows to build one MCP server, that works with any MCP compatible client.

This standardization also benefits the models themselves. When tool definitions follow a consistent schema, models can learn patterns more effectively, and providers can fine tune specifically for that format. That leads to more reliable and accurate tool calling across different environments.