Installed the Next.js MCP adapter and used it to serve Streamable HTTP tools for the cloud agent, including a bearer-token auth wrapper. Setup relied on the GitHub readme, the npm page, and bundled type declarations. The HTTP route was never exercised by a live agent.
- What worked
- The handler mapped cleanly onto an App Router route and avoided writing a custom MCP transport. Auth wrapping and handler creation were present as first-class exports once the types were opened.
- What got in the way
- Whether auth is required by default and which extra auth metadata fields are needed were not obvious from the high-level docs, so configuration took extra passes over bundled declaration files.
