context-saver-mcp
Related Servers
Alternatives to context-saver-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables connecting multiple downstream MCP servers into a single gateway, with unified tool search, namespacing, and deferred loading to preserve context window.26MIT
- AlicenseAqualityBmaintenanceA single MCP server gateway that reduces context bloat by providing progressive tool discovery and invocation, dynamically provisioning downstream servers on demand.26398 PyPI23MIT
- AlicenseNot gradedqualityCmaintenanceA gateway that aggregates multiple MCP servers into a single endpoint, namespacing their tools and forwarding calls, so an agent connects to one MCP to access the entire stack.MIT
- AlicenseNot gradedqualityDmaintenanceMCP Gateway that aggregates multiple upstream MCP servers into a single endpoint with persistent connections, tool registry, and authentication.84 npm2MIT
- AlicenseAqualityAmaintenanceEnables multiplexing multiple MCP servers behind a single gateway connection that lazily loads only the tool schemas needed for the current turn, cutting context usage while providing OAuth authentication, circuit breakers, and hot reload.8MIT
- AlicenseNot gradedqualityCmaintenanceEnables clients to connect once and access the union of multiple backend MCP servers' tools through a single unified interface, with namespaced tool routing, capability search, and health isolation.MIT
TDQS
Scored across 6 tools
Each tool has a distinct role in the gateway lifecycle: discovery, planning, loading, unloading, direct invocation, and status. cs_discover and cs_plan are related but clearly differentiated by catalog listing versus task-specific recommendation.
All tool names follow a consistent cs_ prefix with a clear verb-based convention (discover, plan, load, unload, call, status). The naming is predictable and easy to scan.
Six tools cleanly cover the full lifecycle of discovering, selecting, loading, calling, unloading, and monitoring downstream tools. The set is well-scoped with no redundant entries.
The surface covers discovery, planning, schema loading, direct invocation, unloading, and status/accounting. There are no obvious dead ends for managing context-saving gateway workflows.