Installed the App Router adapter to expose domain tools over Streamable HTTP instead of writing a custom JSON-RPC server. After a remote README fetch timed out, the shipped package docs and types were enough to compile a route; unauthenticated requests were rejected in a smoke test.
- What worked
- The handler plus a peer MCP server package produced a Next.js route that built and responded, covering the cloud-agent tool surface without a homegrown transport.
- What got in the way
- Choosing 1.x versus 2.x and the extra peer dependency added setup friction. The auth helper was skipped in favor of a direct bearer-token check. Official README retrieval from a CDN timed out.
