A
licenseNot graded
qualityD
maintenanceA local-first bridge for moving useful context between coding agents, indexing sessions and creating handoff packets for seamless agent switching.
3
MIT
meld
by lemonaide152
Related Servers
Alternatives to meld
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceShared memory and handoff hub for AI agents, enabling seamless context transfer between sessions with token-budgeted resumes and automatic handoffs.1010 npmMIT
- AlicenseNot gradedqualityCmaintenanceSelf-hosted, zero-knowledge encrypted, self-destructing secrets for secure agent-to-agent coordination3AGPL 3.0
- AlicenseAqualityDmaintenanceShare encrypted, self-destructing secrets from your AI agent. Zero-knowledge E2E encryption. Agent-blind input sources (env:, file:, dotenv:) keep secrets out of LLM context.43 npm1MIT
- AlicenseAqualityDmaintenanceA context preservation engine for AI agents that bundles project state into a markdown package and syncs it to clipboard or cloud, enabling zero knowledge loss across sessions.24 npmMIT
- AlicenseNot gradedqualityCmaintenanceA local-private context-handoff tool for AI agents, preserving decisions, evidence, and verbatim code in a SQLite ledger and providing zone indicators to prevent context rot across sessions.32 npm1MIT
TDQS
A4.4/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct role: create establishes the meld, resolve is for the invited party to submit context, and read is for the owner to retrieve the resolved result. There is no functional overlap between the three operations.
Naming Consistency5/5
All tools follow the same meld_ prefix with a simple verb: create, resolve, and read. This creates a predictable and consistent naming pattern across the entire tool surface.
Tool Count5/5
Three tools is exactly the right scope for an ephemeral context bridge with a straightforward lifecycle. Each tool maps to one essential stage of the meld process with no redundancy.
Completeness5/5
The full lifecycle of a meld is covered: creation, participant resolution, and owner read of the resolved result. Expiry and token rotation are handled automatically, so no additional operations are necessary.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive