[FEATURE] OAuth for hooks/ HTTP hooks

Resolved 💬 3 comments Opened Mar 12, 2026 by liukatkat Closed Mar 16, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

OAuth support for the MCP server is very nice, it handles everything like token refresh. However, there isn't a nice way to do OAuth for HTTP hooks so they can call to endpoints requiring authorization.

Proposed Solution

Now that we have HTTP hooks that can call to endpoints that require authorization, it would be nice if there is also OAuth support for hooks.

Alternative Solutions

Allowing hooks to use the JWT token from the MCP server auth flow could be a good workaround. Related feature request: https://github.com/anthropics/claude-code/issues/25616.

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗