Developer Platform · use case 2

Your terminal, driving work you deployed.

There is almost no interface here on purpose. The client is the one you already have open — point Claude Code at this Worker and five tools appear inside it.

Connect

claude mcp add --transport http tmsquare \
  https://agents-server.tmsquare.net/mcp

Then ask

why did order A-4821 fail, and what should we do about it?

What answers

triage

D1 — the order, what was in it, and the event trail that says why. One Durable Object per order, so the follow-up question is free.

research

Browser Rendering — opens the carrier's page, which knows where the parcel physically is and what happens to it next.

codegen

Dynamic Workers — writes the validation that would have caught this, and runs it in an isolate with no network and no bindings.

The page research opens

Chronopost · CP4472188FR — a stand-in for a carrier that has no API. Open it and it fills in; fetch it and you get the word Loading…, because it renders itself in the browser. That gap is why there is a browser in the drawing.

curl -s .../carrier/track/CP4472188FR | grep -c 2026-11-09   # 0