[pbjerkeseth]

At my work we found lots of these types of memories to be tightly coupled to individual workflows and preferences, and shared things tended to be enforceable by other means (tests/types/linting/review gates). For anything that had team wide alignment, it's hard for me to imagine putting in some 3rd party platform as opposed to committed somewhere or a part of internal mcp tooling.

[mat10112]

Agreed. We started out with that actually at my company. I created a repo that defined our systems taxonomy, how things relate to each other, glossary of terms, etc. Then created an internal MCP to sit in front of it for everyone's agents to use. It did very well initially but eventually became a pretty big burden to maintain especially for the non-technical team members that are not used to the git process for making updates. I wanted to create something that allowed the rest of the non-technical folks to easily contribute to our teams source of truth. Now in memsprout they have their own spaces they create and own so they can manage when, what, and with whom their context is shared.