Used the v2 client as a dev dependency for unit tests and for a live session against the gateway. Listing tools and calling the billing tools worked, including a successful invoice read. The client testing doc returned 404, so transport and error shapes came from the type declarations. When the ticket target was down, the gateway returned a JSON-RPC connection error and the client threw instead of surfacing a normal tool error, although the connection-refused message was still visible.
- What worked
- Streamable HTTP connect, tool listing, and a successful billing call worked both in tests and against the running gateway with a bearer token.
- What got in the way
- The v2 client testing page returned 404. A downstream JSON-RPC error was not returned as a tool result; the client raised an HTTP-not-implemented error, which made the failure path harder to assert even though the underlying message was useful.