From a10272347ce3f087df2cbdcec9f88da2c16a517f Mon Sep 17 00:00:00 2001 From: Blake Bauman Date: Tue, 25 Aug 2026 20:45:43 -0700 Subject: [PATCH 1/2] docs(site,demo): name the revision gap, not a session handshake MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit "2025-era server on the session handshake" separated GitMCP from nothing: all three upstreams answer with a 2025 revision, and demo-tasks hands out an mcp-session-id too — cf-docs is the sessionless one. The phrasing was true when demo-tasks was pinned stateless and has been stale since. What is actually distinctive is the revision gap. GitMCP answers initialize with 2025-03-26, one behind cf-docs and demo-tasks (2025-11-25) and two behind the 2026-07-28 the walkthrough's own curl asks the gateway for. fold negotiates down and the caller never sees the seam, which is the point section 4 was reaching for. Also swaps that section's example repo: modelcontextprotocol/servers answers "No documentation found." — go-sdk returns a real index, and it is the SDK fold is built on. Verified live against demo.fold.run. Co-Authored-By: Claude Opus 5 (1M context) --- apps/demo/src/index.ts | 2 +- apps/docs/src/content/docs/try-the-demo.md | 8 ++++---- apps/site/src/pages/index.astro | 4 ++-- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/apps/demo/src/index.ts b/apps/demo/src/index.ts index a83beac..371c167 100644 --- a/apps/demo/src/index.ts +++ b/apps/demo/src/index.ts @@ -8,7 +8,7 @@ import { Container, getContainer } from '@cloudflare/containers'; // The federation the demo presents. Upstreams are public MCP servers: -// Cloudflare's docs server, GitMCP (2025-era session handshake), and the +// Cloudflare's docs server, GitMCP (pins MCP 2025-03-26), and the // task-minting demo server (apps/demo-tasks — Go, official SDK). const FOLD_CONFIG = { upstreams: [ diff --git a/apps/docs/src/content/docs/try-the-demo.md b/apps/docs/src/content/docs/try-the-demo.md index f1b4651..a517bbb 100644 --- a/apps/docs/src/content/docs/try-the-demo.md +++ b/apps/docs/src/content/docs/try-the-demo.md @@ -10,7 +10,7 @@ description: Walk through demo.fold.run — three public MCP servers behind one | Namespace | Upstream | Notes | |---|---|---| | `cfdocs__*` | Cloudflare's MCP docs server | A real third-party upstream | -| `git__*` | GitMCP | A public 2025-era server on the session handshake — behind the gateway, just another namespace | +| `git__*` | GitMCP | A public upstream a revision behind — behind the gateway, just another namespace | | `jobs__*` | fold-demo-tasks | A task-minting server (Go, on the official SDK); where the [federated-tasks story](https://fold.run/blog/federating-mcp-tasks/) runs live | Every example below is plain `curl`. Responses arrive as a one-event SSE body — read the `data:` line. @@ -83,15 +83,15 @@ curl -s -X POST $DEMO -H "mcp-session-id: $SID" \ No tool name, no routing hint — fold resolves the owner from its affinity index, or by a read-only probe across upstreams for a task it never saw minted (try it: task ids survive sessions, so `tasks/get` from a brand-new session still finds the owner). Mutating methods are never fanned out; `tasks/cancel` and `tasks/result` locate first, then act on the owner alone. The mechanism is the subject of [the launch post](https://fold.run/blog/federating-mcp-tasks/). -## 4. The 2025-era upstream you address the same way +## 4. The older upstream you address the same way ```bash curl -s -X POST $DEMO -H "mcp-session-id: $SID" \ -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' \ - -d '{"jsonrpc":"2.0","id":6,"method":"tools/call","params":{"name":"git__fetch_generic_documentation","arguments":{"owner":"modelcontextprotocol","repo":"servers"}}}' + -d '{"jsonrpc":"2.0","id":6,"method":"tools/call","params":{"name":"git__fetch_generic_documentation","arguments":{"owner":"modelcontextprotocol","repo":"go-sdk"}}}' ``` -GitMCP speaks the 2025-era session handshake. fold — built on the official Go SDK on both sides of the proxy — holds its own client session to it, so from where you're standing it's just another namespace in the same tool list, behind the same governance. +GitMCP still speaks MCP `2025-03-26` — two revisions behind the `2026-07-28` you asked the gateway for at `initialize`. fold — built on the official Go SDK on both sides of the proxy — holds its own client session to it at the version it speaks, so from where you're standing it's just another namespace in the same tool list, behind the same governance. ## 5. Watch it in the console diff --git a/apps/site/src/pages/index.astro b/apps/site/src/pages/index.astro index 491b2d1..2ff3653 100644 --- a/apps/site/src/pages/index.astro +++ b/apps/site/src/pages/index.astro @@ -228,8 +228,8 @@ const jsonld = {

git__*

- GitMCP — a public 2025-era server on the session handshake. Behind the gateway it is - just another namespace. + GitMCP — a public upstream a revision behind the rest. Behind the gateway it is just + another namespace.

From 54ad931e4366a801d0b055bc62d5304a94cc4f77 Mon Sep 17 00:00:00 2001 From: Blake Bauman Date: Tue, 25 Aug 2026 21:00:30 -0700 Subject: [PATCH 2/2] docs(site,docs): name the revision GitMCP pins, and the one it is behind MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit "A 2025-era server on the session handshake" was doing a lot of vague work for a claim that is a single date. Replaced with what the servers actually answer, checked live rather than inferred: GitMCP 2025-03-26 Cloudflare docs 2025-11-25 the fold gateway 2025-11-25 So GitMCP is two revisions behind — 2025-06-18, then 2025-11-25 — and the demo federates it anyway, which is the whole point of the row. The baseline needed correcting. An earlier pass had it as "two revisions behind the 2026-07-28 you asked the gateway for at initialize", which is wrong twice: the gateway does not speak 2026-07-28 — ask for it and it negotiates down to 2025-11-25 — and against 2026-07-28 the gap would be three revisions, not two. The comparison is now against what the gateway actually negotiates, which is also the number a reader checking this would get. The walkthrough's curl examples keep asking for the newer version, because watching it negotiate down is the honest demonstration and the sentence now says so. The two "a revision behind" mentions were undercounting for the same reason and now say two. Blog posts keep the old phrasing; they are dated writing about what ran then. Co-Authored-By: Claude Opus 5 (1M context) --- apps/docs/src/content/docs/try-the-demo.md | 4 ++-- apps/site/src/pages/index.astro | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/apps/docs/src/content/docs/try-the-demo.md b/apps/docs/src/content/docs/try-the-demo.md index a517bbb..148c3ae 100644 --- a/apps/docs/src/content/docs/try-the-demo.md +++ b/apps/docs/src/content/docs/try-the-demo.md @@ -10,7 +10,7 @@ description: Walk through demo.fold.run — three public MCP servers behind one | Namespace | Upstream | Notes | |---|---|---| | `cfdocs__*` | Cloudflare's MCP docs server | A real third-party upstream | -| `git__*` | GitMCP | A public upstream a revision behind — behind the gateway, just another namespace | +| `git__*` | GitMCP | A public upstream two revisions behind — behind the gateway, just another namespace | | `jobs__*` | fold-demo-tasks | A task-minting server (Go, on the official SDK); where the [federated-tasks story](https://fold.run/blog/federating-mcp-tasks/) runs live | Every example below is plain `curl`. Responses arrive as a one-event SSE body — read the `data:` line. @@ -91,7 +91,7 @@ curl -s -X POST $DEMO -H "mcp-session-id: $SID" \ -d '{"jsonrpc":"2.0","id":6,"method":"tools/call","params":{"name":"git__fetch_generic_documentation","arguments":{"owner":"modelcontextprotocol","repo":"go-sdk"}}}' ``` -GitMCP still speaks MCP `2025-03-26` — two revisions behind the `2026-07-28` you asked the gateway for at `initialize`. fold — built on the official Go SDK on both sides of the proxy — holds its own client session to it at the version it speaks, so from where you're standing it's just another namespace in the same tool list, behind the same governance. +GitMCP still speaks MCP `2025-03-26` — two revisions behind the `2025-11-25` this gateway negotiates, whatever you ask for at `initialize`. fold — built on the official Go SDK on both sides of the proxy — holds its own client session to it at the version it speaks, so from where you're standing it's just another namespace in the same tool list, behind the same governance. ## 5. Watch it in the console diff --git a/apps/site/src/pages/index.astro b/apps/site/src/pages/index.astro index 2ff3653..9433f9c 100644 --- a/apps/site/src/pages/index.astro +++ b/apps/site/src/pages/index.astro @@ -228,8 +228,8 @@ const jsonld = {

git__*

- GitMCP — a public upstream a revision behind the rest. Behind the gateway it is just - another namespace. + GitMCP — a public upstream two revisions behind the rest. Behind the gateway it is + just another namespace.