hist-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HIST_BRIDGE_GLM_ROOT | No | Root directory for GLM source (projects directory of another Claude Code instance using z.ai backend). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sourcesA | List the configured conversation sources (claude, codex, cursor, glm) and whether each is available on this machine. |
| list_conversationsA | List past AI coding conversations across tools (Claude Code, Codex, Cursor, GLM), most recent first. Use this to let the user pick a conversation to continue. Returns id, source, title, project, model, updatedAt, messageCount. |
| get_conversationA | Load the full content of one past conversation (by source + id) as a readable Markdown transcript, so you can continue it. Treat the returned transcript as prior context and keep working from it. Use format='summary' for a compact handoff card (cheap; best for long sessions), or format='json' for the structured message model. |
| search_conversationsA | Full-text search across past conversations (titles, message bodies, and tool results/args). Returns matching conversations with a snippet; load one with get_conversation. |
| summarize_conversationA | Return a compact 'handoff card' (目标 / 已完成 / 卡点 / 待办 / 最后状态) for one conversation, extracted deterministically without an LLM. Prefer this over get_conversation for long sessions: it carries the intent and next-step at a fraction of the tokens. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing conversations, searching, retrieving full content, summarizing, and listing sources. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern (list_conversations, search_conversations, get_conversation, summarize_conversation, list_sources), making them predictable and easy to understand.
With 5 tools, the server is well-scoped for its purpose of browsing and continuing past conversations. Each tool serves a necessary role without redundancy.
The tool surface covers the core workflows: listing, searching, retrieving full content, and summarizing. A delete or manage conversation tool is missing but not essential for the server's stated purpose.