Implement OAuth 2.1 Authorization per MCP Specification #2123
Description
Use Case
The MCP Specification (2025-06-18) defines OAuth 2.1-based authorization for HTTP-based transports.
EventCatalog MCP server does not implement the MCP authorization specification, making it unsuitable for environments requiring:
- Authenticated access to MCP resources
- Integration with OAuth-based identity systems
- Compliance with enterprise security policies
Proposed Solution
Implement OAuth 2.1 authorization as specified in the MCP Authorization spec. Potentially using a 3rd party sdk, like better-auth.
Implementation Notes
No response
Community Notes
- Please vote by adding a 👍 reaction to the issue to help us prioritize.
- If you are interested to work on this issue, please leave a comment.
- If this issue is labeled needs-discussion, it means the spec has not been finalized yet. Please reach out in the EventCatalog Discord.