Skip to content

feat: implement MCP Standard 2025-06-18 compliance changes #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dgellow
Copy link
Owner

@dgellow dgellow commented Jun 25, 2025

  • Add WWW-Authenticate headers to 401 responses with configurable realm
  • Add OAuth Protected Resource Metadata endpoint at /.well-known/oauth-protected-resource
  • Use proxy name from config as realm instead of hardcoded value
  • Add urlutil package for proper URL path joining
  • Include comprehensive tests for all new functionality

No breaking changes - fully backward compatible with existing clients.

🤖 Generated with Claude Code

- Add WWW-Authenticate headers to 401 responses with configurable realm
- Add OAuth Protected Resource Metadata endpoint at /.well-known/oauth-protected-resource
- Use proxy name from config as realm instead of hardcoded value
- Add urlutil package for proper URL path joining
- Include comprehensive tests for all new functionality

No breaking changes - fully backward compatible with existing clients.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
@dgellow dgellow changed the title feat: implement MCP Standard 2025-06-18 simple compliance changes feat: implement MCP Standard 2025-06-18 compliance changes Jun 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant