memsprout
Server Details
shared AI-context layer for teams — persistent memory your agents search and update over MCP
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over 58 days
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- memsprout/agents
- GitHub Stars
- 0
TDQS
Scored across 21 tools
Most tools have clearly distinct purposes, with only two pairs of intentional duplicates (fetch/get_memory, search/search_memories) that create minor ambiguity. Descriptions explicitly state they are provided for host compatibility, but an agent might still select the wrong one.
The majority of tools follow a consistent verb_noun pattern. Two tools (fetch, search) use generic names that deviate from the pattern, and memsprout_onboarding uses a different naming style, but overall the naming is predictable and readable.
With 21 tools, the server covers a broad but focused domain of memory management. The count is slightly above the typical range but each tool serves a distinct purpose and earns its place, making it appropriate for the scope.
The tool surface is highly complete: full CRUD for memories, spaces, topics, and assets; multiple upload methods; search and list variants; onboarding and movement. No obvious gaps in core workflows.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
21 tool updates
- First observed
attach_asset - First observed
create_space - First observed
create_topic - First observed
delete_memory - First observed
delete_topic - First observed
detach_asset - First observed
fetch - First observed
get_asset - First observed
get_memory - First observed
get_signed_upload_url - First observed
get_upload_link - First observed
list_memories - First observed
list_spaces - First observed
list_topics - First observed
memsprout_onboarding - First observed
move_memory - First observed
search - First observed
search_memories - First observed
store_memory - First observed
update_memory - First observed
update_topic
Related MCP Connectors
- MemocoreOAuthai.memocore
Shared memory for all your AI agents, your whole team and every MCP client — save, search, recall.
Your memory, everywhere AI goes. Build knowledge once, access it via MCP anywhere.
- ContexelOAuthai.contexel
Shared AI memory. ChatGPT, Claude, Cursor and any MCP app read and write the same memory.
Persistent AI memory shared across Claude, ChatGPT, coding agents, and compatible MCP clients.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceSelf-hosted personal context layer that gives AI agents shared memory via MCP.MIT
- AlicenseNot gradedqualityDmaintenanceShared memory for any MCP-compatible AI, enabling cross-platform knowledge persistence and retrieval so users' context, preferences, and project info follow them everywhere.3AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceProvides persistent, shared memory for AI agents via MCP, enabling retrieval of relevant memories instead of loading entire context. Allows agents across projects, machines, and tools to share a single auditable, markdown-native brain.3AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceGoverned shared memory platform for AI agents and agent fleets. Provides persistent memory, cross-agent knowledge sharing, permissions, audit trails, and multi-tenant isolation through a Model Context Protocol (MCP) server.4 npm497Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.