Skip to main content
Glama
trust-delta

Conversation Handoff MCP

by trust-delta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HANDOFF_SERVERNoServer connection mode: 'none' for standalone, or explicit server URL (e.g., 'http://localhost:3000'). Default is auto-discovery mode.
HANDOFF_MAX_COUNTNoMaximum number of handoffs100
HANDOFF_PORT_RANGENoPort range for auto-discovery1099-1200
HANDOFF_SERVER_TTLNoServer auto-shutdown after inactivity in milliseconds (0 = disabled). Default is 24 hours.86400000
HANDOFF_RETRY_COUNTNoAuto-reconnect retry count30
HANDOFF_MAX_KEY_LENGTHNoMaximum key length100
HANDOFF_RETRY_INTERVALNoAuto-reconnect interval in milliseconds10000
HANDOFF_MAX_TITLE_LENGTHNoMaximum title length200
HANDOFF_MAX_SUMMARY_BYTESNoMaximum summary size in bytes (default 10KB)10240
HANDOFF_MAX_CONVERSATION_BYTESNoMaximum conversation size in bytes (default 1MB)1048576

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

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
handoff_saveA

Save a conversation handoff for later retrieval. Use this to pass conversation context to another AI or project.

Format Selection

  • structured (default): Organize content using the template below. Much faster — reduces output tokens to ~5-20% of the original conversation. Best for most handoffs.

  • verbatim: Save the complete word-for-word conversation. Use only when exact wording matters (e.g., legal text, precise error messages).

Structured Template (for format="structured")

## Key Decisions
- [Decision]: [Rationale]

## Implementation Details
[What was built/changed, with relevant code snippets]

## Code Changes
[Files modified with brief description]

## Open Issues
- [Issue]: [Status/Context]

## Next Steps
- [ ] Action item

Omit sections that don't apply. Add custom sections if needed.

handoff_listA

List all saved handoffs with summaries. Returns lightweight metadata without full conversation content. Opens interactive UI if supported.

handoff_loadB

Load a specific handoff by key. Returns full conversation content.

handoff_clearB

Clear handoffs. If key is provided, clears only that handoff. Otherwise clears all.

handoff_statsB

Get storage statistics and current limits. Useful for monitoring usage.

handoff_restartA

Restart the shared HTTP server. Useful when the server is in an unhealthy state. All stored handoffs will be lost (data is in-memory).

handoff_mergeB

Merge multiple handoffs into one. Combines conversations and metadata from related handoffs into a single unified handoff.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
ui://conversation-handoff/viewer.html
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: clear, list, load, merge, restart, save, and stats cover unique operations. The descriptions specify different actions (e.g., clearing vs. loading vs. merging), making misselection unlikely.

Naming Consistency5/5

All tools follow a consistent 'handoff_verb' pattern (e.g., handoff_clear, handoff_list, handoff_load). This verb_noun structure is uniform throughout, with no deviations in style or casing, making the set predictable and readable.

Tool Count5/5

With 7 tools, the count is well-scoped for managing conversation handoffs. Each tool serves a specific function (e.g., saving, loading, clearing, merging), and none feel redundant or missing, fitting the domain's lifecycle needs appropriately.

Completeness5/5

The tool set provides complete CRUD-like coverage for handoff management: save, load, list, clear, merge, restart, and stats. This covers the full lifecycle from creation to deletion, with no obvious gaps for the stated purpose of handling conversation handoffs.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources