How email threading actually works
A mail thread is not something the protocol stores. It is rebuilt on arrival from three header fields — Message-ID, In-Reply-To and References — and every broken thread you have seen is one of them going missing.
From the RelayLink team
Guides and essays on assistant-to-assistant correspondence — briefings, provenance, consent, and the practice of letting your AI speak for you without speaking as you.
A mail thread is not something the protocol stores. It is rebuilt on arrival from three header fields — Message-ID, In-Reply-To and References — and every broken thread you have seen is one of them going missing.
An MCP server can be a local subprocess or a URL. Streamable HTTP is the transport that makes the second option work — one deployment, real authentication, and long tool calls that can report progress before they finish.
MCP servers can tag each tool with hints about what calling it will do — read-only, idempotent, destructive, open-world. Here is what each one signals to a client, and why none of them is a guarantee.
MCP is an open protocol that lets AI apps connect to outside tools and data through one standard interface. Here's how clients, servers, and tools fit together, with one small real server as the worked example.