smart-fork
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fork-detectB | Search for relevant past Claude Code sessions to fork from |
| get-session-previewB | Get a preview of a session's content before forking |
| record-forkB | Record a fork event for history tracking (internal tool, usually auto-called) |
| get-fork-historyC | Get history of recently forked sessions |
| add-session-tagB | Add a tag to a session for organization and categorization |
| remove-session-tagC | Remove a tag from a session |
| list-session-tagsB | List tags for a session or all tags in the system |
| get-similar-sessionsB | Find sessions similar to a given session (for detecting duplicates or related work) |
| get-session-summaryA | Get a quick summary of a session's content without reading the full session |
| compare-sessionsA | Compare two sessions to identify common content, unique messages, and differences in topics/technologies |
| cluster-sessionsB | Automatically cluster sessions by topic using k-means on session embeddings |
| get-session-clustersB | Get all session clusters and their metadata |
| get-cluster-sessionsB | Get all sessions in a specific cluster |
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 13 tools
Each tool targets a distinct operation: tags (add/remove/list), clustering (cluster/get-cluster-sessions/get-session-clusters), forking (detect/record/history), and session details (preview/summary/compare/similar). No two tools have overlapping purposes.
All tools use a consistent kebab-case verb-noun pattern, e.g., add-session-tag, cluster-sessions, get-fork-history. The style is uniform and predictable.
With 13 tools, the server covers the core workflows of session forking, clustering, tagging, and comparison without being bloated or sparse.
The tool surface covers the main lifecycle: fork detection, recording, history, preview, summary, clustering, tagging, and comparison. A minor gap is the lack of a direct list-all-sessions tool, but sessions can be accessed through clusters or similarity.