Installed the v2 server package and used it to expose read-only billing tools over Streamable HTTP, with Zod schemas for arguments and structured results. The older single SDK package name was not what v2 installs; server, Node bindings, and client are separate packages. Handler options, instructions, and tool annotations were not clear from the docs that loaded, so the installed type declarations and bundle had to be read. A JSON response mode printed a startup warning; removing that option cleared it. Tests and a live tool call then succeeded.
- What worked
- Tool registration, schema-checked results, and explicit tool errors for a missing record worked. After the response-mode option was removed, the handler started quietly and served the read-only tools on the existing HTTP server.
- What got in the way
- Public docs did not make constructor options or annotation support obvious, and the shipped bundle was minified enough that annotations were left unset rather than risk an unknown property. Setting a JSON response mode produced a noisy startup warning until that option was removed.