feat(nitro): accept oauth on mcp() - #331
Merged
Merged
Conversation
2 tasks
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
2 tasks
Contributor
|
Thank you for following the naming conventions! 🙏 |
`mcp({ oauth })` protects a file-based endpoint without a route file. The
module generates the `createMcpOAuth` call into its own virtual module,
wires it as the handler's `auth`, and mounts the RFC 9728
protected-resource document on the path derived from `resource`.
`oauth` and `auth` cannot both be set on one endpoint, and a config
without a JWKS URL throws while the app is being built rather than
accepting everything at runtime.
HugoRCD
force-pushed
the
feat/nitro-oauth-module-option
branch
from
September 4, 2026 08:57
5b7b0a9 to
b6abfe6
Compare
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📚 Description
Stacked on #330.
mcp({ oauth })protects a file-based endpoint without a route file. The module generates thecreateMcpOAuthcall into its own virtual module, wires it as the handler'sauth, and mounts the RFC 9728 protected-resource document on the path derived fromresource— so a client that gets a401can find where to authenticate without any wiring on your side.oauthandauthcannot both be set on one endpoint, and a config without a JWKS URL throws while the app is being built rather than accepting everything at runtime.This is the second exception to "
mcp()options are data": they cross into generated code as JSON, so avalidatecallback still means a route file, but JWT verification can be generated.📝 Checklist