Skip to content

Add HTTPS support for secure local development #482

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

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

Conversation

bbn
Copy link

@bbn bbn commented Jun 2, 2025

Summary

• Add HTTPS server support for both client UI and proxy server to enable secure local development
• Implement environment variable configuration with INSPECTOR_SSL_CERT_PATH and INSPECTOR_SSL_KEY_PATH
• Include automatic fallback to HTTP when SSL certificates are missing or invalid
• Add cross-platform SSL certificate generation script supporting macOS, Linux, and Windows

Motivation

OAuth flow testing requires digest security libraries that are restricted to HTTPS-only scenarios for security reasons. This enhancement enables proper OAuth testing in the MCP Inspector by providing secure HTTPS endpoints.

Test plan

  • Generate SSL certificates using ./generate-ssl.sh
  • Set environment variables and verify HTTPS endpoints work
  • Test fallback behavior with missing/invalid certificates
  • Verify HTTP mode still works without environment variables
  • Test certificate generation script on different platforms

- Implement HTTPS server support for both client and proxy server
- Add INSPECTOR_SSL_CERT_PATH and INSPECTOR_SSL_KEY_PATH environment variables
- Include fallback to HTTP when SSL certificates are missing or invalid
- Add cross-platform SSL certificate generation script
- Update documentation with HTTPS configuration instructions
@olaservo
Copy link
Member

olaservo commented Jun 5, 2025

Hi, I see that you have a test plan listed, did you actually test this yet or should it still be in draft mode?

@bbn
Copy link
Author

bbn commented Jun 6, 2025

Hi, I see that you have a test plan listed, did you actually test this yet or should it still be in draft mode?

I've tested everything except the multi-platform aspects.

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.

2 participants