session-bridge
Related Servers
Alternatives to session-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides context from previous sessions to new OpenCode sessions for continuity in the same project.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to search and retrieve past chat history from Claude.ai exports and Claude Code sessions, allowing the AI to reference previous conversations and decisions.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI coding assistants like Claude Code, Cursor, and Codex to share chat logs, terminal history, and session context with each other. Eliminates the need to re-explain context when switching between different AI coding tools.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to retrieve a bounded context packet linking relevant code with prior session evidence, decisions, failures, and fixes from local Codex and Claude Code history.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables Codex to list and read saved Claude Code conversations, retrieve incremental context updates before replies, and optionally ask Claude text-only follow-up questions within a selected session without disrupting the workflow.10MIT
- FlicenseAqualityDmaintenanceBridges Claude Design projects into existing Claude Desktop sessions by fetching code files, chat history, and project bundles.71-
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: list_sessions for discovery/selection, read_session for viewing display text, and prepare_handoff for bringing session context into the current tool. The sequential workflow avoids overlap.
All tool names follow the same verb_noun pattern in snake_case: list_sessions, read_session, prepare_handoff. This is consistent and predictable.
Three tools is well-scoped for a session-bridge server focused on a narrow use case. Each tool is necessary and the set is neither bloated nor thin.
The core workflow of discovering, reading, and transferring session context is fully covered. The server's purpose is a bridge, not session management, so no missing CRUD operations are apparent.