Context Bridge
Related Servers
Alternatives to Context Bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to semantically search your entire local conversation history from Claude Desktop, ChatGPT and Claude Code, and to retrieve, browse, ingest and report on those conversations. All embeddings run locally, so no cloud, API keys, or data leave your machine.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables local, read-only keyword search across past Claude Code, Codex, Gemini CLI, and ChatGPT conversations plus markdown notes, with exact source citations and context retrieval.MIT
- AlicenseAqualityDmaintenanceSemantic search across Claude Code conversations. Hybrid vector + keyword search, fully local, background indexing.628 npm11MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search and retrieve past coding-tool conversations across Claude Code, Claude Desktop, Codex, and Cursor through a local, read-only index.2MIT
- AlicenseBqualityDmaintenanceEnables searching and browsing of Claude conversation history with hybrid search combining full-text, Spotlight, and optional vector embeddings.101MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to search locally indexed exported chat history and project docs, retrieving full messages and conversation IDs via full-text search.1MIT
TDQS
Scored across 2 tools
context_search retrieves candidate passages while context_read expands a specific record_id into surrounding turns. The descriptions explicitly define the handoff between them (search produces record_id, read consumes it), leaving no realistic chance of misselection.
Both tools use the same context_ prefix plus a clear retrieval verb (search, read), forming a predictable two-verb pattern. There is no mixing of conventions or casing.
Two tools is on the thin side, but for a read-only bridge that only needs discovery plus passage expansion, each tool has a distinct job and nothing extraneous is present. It is slightly under the typical 3-15 range but not mismatched to scope.
Search plus read covers the core retrieve-and-expand lifecycle, including pagination, context windows, and integrity checks. Minor gaps remain around enumerating indexed sources or conversations without issuing a search query, but agents can work around this.