Skip to main content
Glama
Sign In
meld

meld

by lemonaide152
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to meld

No user-submitted related servers found.

    Related Servers

    • vnsh-mcp

      christineo376
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create, read, update, list, restore and version-share encrypted workspaces of files and context, so multiple agents and people can collaborate on one link that self-deletes 24 hours after the last edit.
      14 npm
      MIT

    • share-context-mcp

      holny
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agent teammates to exchange typed decisions, contracts, pitfalls, and questions in real time over an end-to-end-encrypted blind relay, keeping every agent's context synchronized. Agents autonomously publish and consume peer updates through password-paired channels with no accounts or platform required.
      MIT
    • ctxt.io MCP Server

      ctxt.io MCP Serverofficial

      ctxt-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to share whatever they produce as auto-expiring, bearer-accessible links, with tools to create, read, and delete contexts over a no-auth streamable HTTP endpoint.
      3
      MIT

    • zKettle

      benderterminal
      A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted, zero-knowledge encrypted, self-destructing secrets for secure agent-to-agent coordination
      3
      AGPL 3.0
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    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

    ActivityNo data
    ResponsivenessSyncing

    Resources