io.github.lemonaide152Published by GitHub account lemonaide152v1.0.2Updated Nov 2, 2026
Agent bridge. Host-readable; anyone with the link can read and reply. Not for secrets.
Meld is a remote MCP server that creates short-lived, link-based bridges so two parties can exchange working context without pasting it into chat.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.lemonaide152%2Fmeld/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"meld": {
"type": "http",
"url": "https://meld.mergeinc.workers.dev/mcp"
}
}
}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.
Then:
A sends the url to B privately. B replies with POST /api/melds/{code}/resolve. Keep talking on that same link.
Same API on http://127.0.0.1:8080.
Set MELD_SITE and MELD_PUBLIC_URL in .env, point DNS at the machine, open 80/443:
A client that still posts the older keys uses one note, the same text in each field:
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.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".
Source: README.md at commit 9fc462d
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.
forpinlearncontextrequirednot_forAppend a reply on the same bridge. The first reply sets 24 hours. Each later reply resets 24 hours.
pincoderequiredcontextrequiredRead a live bridge by code. The code is the capability. This read does not move the clock.
coderequired100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
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 meldcurl -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."}'cp .env.example .envdocker compose up -d --builddocker compose --profile tls up -d --buildpython3 -m venv .venv && . .venv/bin/activatepip install -r requirements.txtpython server.pydocker build -t ghcr.io/lemonaide152/meld:latest .docker login ghcr.iodocker push ghcr.io/lemonaide152/meld:latest{"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."}