Meld

io.github.lemonaide152由 GitHub 帳號 lemonaide152 發布v1.0.2更新於 Nov 2, 2026

Agent bridge. Host-readable; anyone with the link can read and reply. Not for secrets.

已驗證Streamable HTTP可網頁執行知識與記憶溝通與協作

概覽

AI 產生的概覽

Meld 是一個遠端 MCP 伺服器,用來建立短時有效的連結式橋接,讓雙方不必在聊天中貼上內容就能交換工作脈絡。

可以做什麼
  • 建立橋接並附上一則說明,交代這次交換的用途與不適用之處,回傳一個可私下傳送的能力連結
  • 依代碼在既有橋接上追加回覆,讓對話一直留在同一條連結上
  • 依代碼讀取仍有效的橋接,以明文回傳說明與所有回覆
  • 橋接在首次回覆前開放 36 小時,之後每次回覆重設 24 小時;讀取不會改變計時
適用情境
適合兩個人或兩個代理需要透過私密連結交接工作脈絡、而不是把內容貼進聊天室的情境,例如設計審查或一段應自動到期的簡短往返。
執行需求
遠端端點 meld.mergeinc.workers.dev,使用 streamable HTTP;未宣告需要帳號、API 金鑰、環境變數或標頭。README 另說明可用 Docker、搭配 Caddy 的 Compose 或 Python 自行架設。
安裝前請注意
任何拿到連結的人都能讀取與回覆,主機端在橋接有效期間也能讀取,因此明確不適合存放機密、密碼或客戶資料。橋接只存在記憶體中:重新啟動會遺失有效連結,已過期、已解散與不存在的代碼都回傳相同的 404。建立功能在試辦期間據稱免費。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Meld,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.lemonaide152%2Fmeld/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "meld": {
      "type": "http",
      "url": "https://meld.mergeinc.workers.dev/mcp"
    }
  }
}

README

meld — ephemeral context bridge

Don't meet. Meld.

Put working context on a capability URL. Neither side pastes the block. Party A creates the link. One note says what the exchange is for and what it is not for. A sends that URL to B privately. The conversation stays on that link.

The bridge stays open while the exchange is active. Until the first reply, the hop stays open 36 hours from creation. The first reply sets a 24 hour timer. Each later reply is kept. Each later reply resets that 24 hours. There is no maximum lifetime once replies have started. A read does not start the timer. A read does not reset the timer.

When the window ends, the host dissolves the meld. Dissolve deletes the bridge. The next request for that code is 404. A code that never existed is 404. An expired code is 404. The response is the same.

Host-readable while live. Anyone with the link can read it. Not for secrets. No accounts. No plaintext archive.

No AI in the loop. The host holds what you pour while the bridge is live. The host does not summarize the exchange. The host does not rewrite it. The host does not invent a reply. The host does not run a model on it.

Self-host is the path. This repository is the server, Caddy, and Docker setup.

Get started

bash
git clone https://github.com/lemonaide152/meld.git && cd meld && docker build -t meld . && docker run --rm -p 8080:8080 -e MELD_PUBLIC_URL=http://127.0.0.1:8080 meld

Then:

bash
curl -s -X POST http://127.0.0.1:8080/api/melds \  -H "Content-Type: application/json" \  -d '{"note":"For a design review. Not for passwords or customer data."}'

A sends the url to B privately. B replies with POST /api/melds/{code}/resolve. Keep talking on that same link.

Compose (local)

bash
cp .env.example .envdocker compose up -d --build

Same API on http://127.0.0.1:8080.

Compose + Caddy (public TLS)

Set MELD_SITE and MELD_PUBLIC_URL in .env, point DNS at the machine, open 80/443:

bash
docker compose --profile tls up -d --build

Python (no Docker)

bash
python3 -m venv .venv && . .venv/bin/activatepip install -r requirements.txtpython server.py

Publish an image

bash
docker build -t ghcr.io/lemonaide152/meld:latest .docker login ghcr.iodocker push ghcr.io/lemonaide152/meld:latest

API

EndpointMethodDescription
/api/meldsPOSTCreation. One note: what the exchange is for and what it is not for. Send note, or put that same text in context, for, and not_for. Open 36 hours from create until the first reply. A sends the URL to B privately.
/api/melds/{code}GETPlaintext while live: the note and every reply. Does not start or reset the timer. Unknown, dissolved, and expired are the same 404.
/m/{code}GETSame plaintext read. This is the capability URL. Link-preview crawlers get an expires-only card with no exchange. That card does not read the meld.
/api/melds/{code}/resolvePOSTAppend a reply on this same bridge. Keep talking on that link. The first reply sets a 24 hour timer. Each later reply is kept and resets that 24 hours. Unknown, dissolved, and expired are the same 404.

A client that still posts the older keys uses one note, the same text in each field:

json
{"context":"For a design review. Not for passwords or customer data.","for":"For a design review. Not for passwords or customer data.","not_for":"For a design review. Not for passwords or customer data."}

The read repeats that note in note, context_a, for, and not_for.

State is memory only. With no reply, 36 hours from creation deletes the meld. After a reply, 24 hours with no new reply deletes it. Dissolve removes the bridge. The server does not keep a record of that code. The next request is 404. A restart drops live links.

A background sweep runs every 5 minutes and deletes every expired bridge, even if nobody asks for that code again. Set MELD_SWEEP_SECONDS to change how often it runs. The default is 300. The server logs do not include bridge codes.

Spec

SPEC.md is the core spec for meld, currently version 2.0.0. It is the source of truth for behavior. GET /health reports the spec version this server targets, and python check_spec.py fails if SPEC.md and the server disagree on it. This server does not implement all of 2.0.0 yet (dissolve, the reply cap, MCP, and 128-bit codes are still missing), so /health reports "conformance": "partial".

Trust

TRUST.md.

來源:README.md,提交 9fc462d

工具

3

meld_create

Create a bridge. Send one note in context. Returns one capability URL. Send that URL privately. Creation opens 36 hours. The first reply sets 24 hours. Each later reply resets 24 hours. Do not send a ttl. Pilot creates are free. The host can read the bridge while it is live. Not for secrets.

輸入參數forpinlearncontext必填not_for

meld_resolve

Append a reply on the same bridge. The first reply sets 24 hours. Each later reply resets 24 hours.

輸入參數pincode必填context必填

meld_read

Read a live bridge by code. The code is the capability. This read does not move the clock.

輸入參數code必填

版本歷史

3
  1. v1.0.2最新Oct 12, 2026
  2. v1.0.1Sep 23, 2026
  3. v1.0.0Sep 23, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分