pond
Related Servers
Alternatives to pond
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server that lets AI agents query their own LLM call history as a branchable DAG and offload conversation context into immutable, AES-256-GCM-encrypted capsules — restorable in full or per segment, crypto-shreddable, with RAID-style replication. 12 tools, no API keys, no cloud.108 npm3MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first memory daemon for AI coding agents that captures session transcripts, distills typed memories (decisions, facts, lessons, commands, todos), and serves them via hybrid search through MCP tools.88 npmMIT
- AlicenseAqualityBmaintenanceA local-first, privacy-first MCP server that passively indexes personal digital activity (screenshots, clipboard, notes, downloads, links) into a local database, enabling LLMs like Claude to access your context without cloud storage.4MIT
- FlicenseNot gradedqualityBmaintenanceLocal-first memory for AI coding agents. Indexes your Claude Code, Codex, Cursor, Cline and Gemini CLI history by repo/branch/worktree and hands a context capsule (decisions, touched files, next steps) to the next agent over MCP.-
- AlicenseAqualityBmaintenanceCognitive prosthetic for AI agents. Indexes conversation history from ChatGPT, Claude Code, Cursor, and Gemini CLI into searchable embeddings. 25 MCP tools including tunnel_state (resume where you left off), switching_cost (quantify context-switch penalty), thinking_trajectory (track idea evolution), and alignment_check (decisions vs principles). LanceDB + Parquet, 12ms recall, local-first.2574MIT
- FlicenseNot gradedqualityAmaintenanceLocal MCP server that lets your AI coding agent query its own cross-tool project history - file/command freshness, past test failures, cost & token spend, cache status, and session handoff - over stdio, 100% local, no telemetry.46-
TDQS
Scored across 4 tools
Each tool targets a distinct purpose: pond_search for discovery, pond_get_message for single-message expansion, pond_get_session for full-session transcripts, and pond_sql for advanced SQL queries. The descriptions make the boundaries clear, and there is no overlap in functionality.
All tools share the pond_ prefix and use snake_case, but the pattern is not perfectly uniform: two use get_ (pond_get_message, pond_get_session), one uses a bare verb (pond_search), and one uses a noun (pond_sql). This is mostly consistent but with a slight deviation.
Four tools is well within the ideal 3-15 range for a focused server. Each tool earns its place: search, single-message read, session read, and SQL access cover the core recall/analytics functionality without redundancy.
The set provides a complete workflow for recalling past conversations: search to find, then either get a message or get a session to read, with SQL as an escape hatch for advanced queries, exact matching, and analytics. The documented gaps (tool bodies, subagent sessions) are explicitly addressed via SQL, so there are no dead ends.