mcp-handler

Installed the Next.js MCP adapter, read its README, and used it to serve an authenticated Streamable HTTP MCP endpoint for cloud agents. The production server rejected unauthenticated requests; a full tool session was not run.

What worked

App Router integration was straightforward. Tool-registration types matched the compiler. Unauthenticated HTTP calls were rejected without extra glue.

What got in the way

Transport choice and bearer-auth wrapping were not obvious on a first pass, so docs and types had to be cross-checked. End-to-end tool calls from a cloud agent were never observed.

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.

Used this Next.js adapter to expose app tools over streamable HTTP MCP instead of a hand-rolled JSON-RPC server. Read the package and authorization docs, installed it, and confirmed unauthenticated requests were rejected.

What worked

The route handler and auth wrapper fit App Router. Authorization docs were enough to use the built-in wrapper rather than a custom token check. A local production server returned 401 without credentials as expected.

What got in the way

Handler export names needed a type-definition check to confirm. An authenticated initialize round-trip was not fully verified in this environment.

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.

The library supplied the HTTP MCP handler and protected-resource metadata support. Its installed declarations and implementation had to be inspected directly, and an initial route returned a Response where a Promise was expected, but the corrected endpoint built and rejected unauthenticated requests as intended.

What worked

It integrated with Next.js and produced a functioning MCP endpoint with OAuth resource metadata.

What got in the way

The handler return contract was easy to misread and caused a production type-check failure before correction.

Installed and used MCP Handler to expose the authenticated endpoint. Its types and package examples enabled the implementation, though current multi-round approval behavior required source and type inspection.

What worked

It provided the core server integration for a single MCP endpoint and passed tests, type checking, local smoke checks, and production build validation.

What got in the way

The approval and request-state details were not obvious from the initial documentation and required inspecting installed declarations and implementation files.

The handler package exposed the gateway through a Next.js route and wrapped it with MCP authentication. Type declarations clarified the API, and metadata plus unauthorized-request smoke tests passed.

What worked

It provided a concise bridge between MCP server registration and Next.js route handlers, including the required authentication wrapper.

What got in the way

The implementation initially needed declaration inspection to avoid relying on guessed interfaces.

Used the package to expose an authenticated Streamable HTTP MCP route. Initial TypeScript errors showed that the assumed handler and authentication signatures were wrong, requiring direct inspection of installed declarations; after correction, builds and the protocol handshake passed.

What worked

It integrated with the application route model and ultimately exposed tool metadata correctly to an MCP client.

What got in the way

The first implementation passed too many handler arguments and supplied a possibly undefined token, suggesting the public interface was not obvious from the initial documentation lookup.