mcp-priostack
Related Servers
Alternatives to mcp-priostack
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceSelf-hosted personal context layer that gives AI agents shared memory via MCP.MIT
- FlicenseNot gradedqualityBmaintenanceProvides a zero-dependency MCP interface that equips personal AI agents with agenda tracking, autonomous sandbox execution, ambient cue handling, fast reflex intent processing, and episodic memory.7-

Structured-shofficial
AlicenseNot gradedqualityDmaintenanceMCP server providing managed persistent memory for AI agents. Read and write structured state across sessions, tools, and restarts at 1000+ requests per second, with no infrastructure to self-host or operate.2Apache 2.0- AlicenseNot gradedqualityCmaintenanceLocal context management, search engine, and memory for agentic AI via MCP, enabling efficient context retrieval and storage.38 npm5MIT
- AlicenseCqualityAmaintenanceProvides AI agents with a human-inspired memory layer via MCP, enabling episodic and semantic memory recall, forgetting curves, consolidation, and contradiction detection. It integrates with MCP clients to offer local-first, dependency-free memory management.981MIT
- 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
TDQS
Scored across 40 tools
Many tools have overlapping or highly specialized purposes that are hard to distinguish without deep domain knowledge (e.g., noetic.observe vs noetic.query vs noetic.reason vs noetic.ground; noetic.propose vs noetic.simulate vs noetic.materialize). The descriptions use dense jargon, making it difficult for an agent to reliably select the right tool.
The naming is mostly consistent with a noetic. prefix and verb-style names (connect, disconnect, query, commit, grant, revoke). However, some names are abstract or inconsistent in style (e.g., noetic.orient, noetic.territory, noetic.focus, noetic.ground) and don't follow a clear verb_noun pattern like others.
40 tools is a very large surface for a single server, and many tools are highly specialized or overlapping. While the server appears to cover a complex domain, the count feels excessive and would likely overwhelm an agent, especially with many niche operations (e.g., noetic.orient, noetic.territory, noetic.metrics).
The tool set covers a broad lifecycle: registration, connection, spaces, grants, access requests, assertions, checkpoints, commits, and receipts. There are some potential gaps (e.g., no explicit tool for deleting a space or revoking a session), but the surface is fairly comprehensive for the apparent domain.