openport
Related Servers
Alternatives to openport
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA portable self-hosted memory layer for AI tools, storing context, memories, and handoffs for access from any MCP-compatible client.48 npmMIT
- AlicenseNot gradedqualityDmaintenanceA portable MCP server providing a shared intelligent memory system for any MCP-compatible AI tool, enabling storage, retrieval, extraction, and governance of memories across sessions.16 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP-native, local-first memory server that gives AI agents persistent, structured memory across sessions and tools, enabling them to maintain identity and context without reconfiguration.3MIT
- AlicenseNot gradedqualityBmaintenanceProvides a self-hosted shared memory service that lets AI agents capture and recall durable facts, decisions, and context across multiple tools and MCP-capable clients.3MIT
- AlicenseNot gradedqualityBmaintenanceA vendor-independent memory layer MCP server that enables multiple LLMs and AI agents to share and persist personal memories, knowledge, and context across sessions, with support for full-text search and tagging.ISC
- AlicenseAqualityBmaintenanceA self-hosted MCP memory server that gives every MCP-compatible agent a shared, persistent memory layer, so preferences, project conventions, and past decisions carry across sessions and across different agents and vendors. It combines hybrid keyword-plus-vector retrieval with automatic context injection, zero-config sync, and selective injection of memories by agent and priority.202MIT
TDQS
Scored across 11 tools
The tools separate sessions, context, docs, and skills, but several boundaries overlap: start_session vs learn_workflow vs get_context, and finish_session vs update_context. The descriptions explicitly tell agents to prefer one tool over another, which helps, but also confirms there is real ambiguity in selection.
Most names follow a clear snake_case action_resource pattern: start_session, get_doc, update_skill, collapse_context. The main deviations are ping as a conventional health-check name and a mix of verbs like start/finish/learn, but the convention remains predictable overall.
Eleven tools is a reasonable size for a session/memory/workflow server, covering health, sessions, context, docs, and skills without becoming oversized. However, some tools appear redundant enough that consolidation could reduce the count slightly.
The surface covers session lifecycle, context reading/writing/pruning, docs reading/writing, skills reading/writing, and health checks. There are minor gaps such as no explicit delete/remove operation for docs, skills, or context entries, but core workflows are covered.