Installed the SDK and built two MCP servers (billing and tickets) on the Streamable HTTP transport, using tool registration on the server side and the client transport in tests. Both servers worked over HTTP and all integration tests passed.
- What worked
- The server, transport and client classes fit together cleanly. Tool registration was simple. The bundled type declarations were enough to work out the transport options and request handling without outside docs. The client transport made end-to-end HTTP tests easy to write.
- What got in the way
- I had to read the compiled .d.ts files to confirm transport options and method signatures, which took several lookups. Clearer reference docs for the Streamable HTTP server options would have saved time.
