feat(nitro): add clerk, okta and workos oauth connectors - #332
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
2 tasks
Contributor
|
Thank you for following the naming conventions! 🙏 |
HugoRCD
force-pushed
the
feat/nitro-oauth-connectors
branch
from
September 4, 2026 08:57
3d64df0 to
f5578cd
Compare
commit: |
Each connector fills in one provider's issuer conventions and returns the
same options object `mcp({ oauth })` and `createMcpOAuth` already accept,
so using a provider is one call rather than a JWKS URL looked up by hand.
They sit on their own subpaths — `nitro-mcp-toolkit/oauth/clerk`,
`/okta`, `/workos` — so an app that imports none of them never loads
them. `clerk` reads `CLERK_PUBLISHABLE_KEY`, skips audience validation
because Clerk puts the OAuth client in `azp`, and proxies RFC 8414
metadata for clients that only look on the resource origin. `okta`
covers custom authorization servers, `workos` covers AuthKit, where
`aud` is the client id rather than the MCP URL.
HugoRCD
force-pushed
the
feat/nitro-oauth-connectors
branch
from
September 4, 2026 09:16
f5578cd to
22b4150
Compare
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 #331. Last of the three OAuth PRs.
Each connector fills in one provider's issuer conventions and returns the same options object
mcp({ oauth })andcreateMcpOAuthalready accept, so using a provider is one call rather than a JWKS URL looked up by hand.They sit on their own subpaths —
nitro-mcp-toolkit/oauth/clerk,/okta,/workos— so an app that imports none of them never loads them.clerkreadsCLERK_PUBLISHABLE_KEYfor the issuer and JWKS, skips audience validation because Clerk puts the OAuth client inazp(useauthorizedPartiesinstead), and proxies RFC 8414 metadata for older clients that only look on the resource origin.oktacovers custom authorization servers and derives JWKS from the issuer. Org-server tokens are opaque, so they are out of scope.workoscovers AuthKit, whereaudis the client id rather than the MCP URL.Adds three
package.jsonsubpath exports and three build entries.📝 Checklist