feat(mcp): add standard Clerk-backed OAuth - #15
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e3bf87c8f8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
All reported issues were addressed across 33 files
Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.
Re-trigger cubic
There was a problem hiding this comment.
All reported issues were addressed across 22 files (changes from recent commits).
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
Summary
/mcpendpoint with standard OAuth 2.1 and Clerk sign-inCompatibility and cleanup
2026-07-28with stateless compatibility for current 2024/2025 clients/mcp-v2route, fixed Clerk client workaround, custom CLI, and beta scripts/mcpas the only MCP endpointTesting
bun test tests/mcp-server/mcp-auth.test.ts tests/mcp-server/oauth-authorization.test.ts tests/web/auth-navigation.test.ts(23 passing)bun run typecheckbun run buildbun run lint(passes with the existing unrelated warning inscripts/ingest-xsd/ingest.ts:34)bunx wrangler deploy --dry-runfromapps/mcp-serverProduction E2E passed after a Wrangler deployment: Codex registered dynamically, completed Clerk sign-in and branded consent, exchanged the code, initialized MCP, discovered the tools, and called
ooxml_elementforw:p. The usage event was stored with the Clerk user ID, dynamic client ID, tool, and timestamp.