Hi team,
In some enterprise environments, it’s necessary to trust internal or self-signed certificates for HTTPS traffic. To make HTTPS requests within Cursor work properly, we currently have to launch Cursor with custom environment variables like:
SSL_CERT_FILE=/path/to/cert.pem cursor
This works, but it’s not ergonomic and causes issues in environments where users don’t control how Cursor is launched (e.g., via system launchers or desktop shortcuts).
What I’m requesting:
It would be very helpful if Cursor supported a way to configure SSL_CERT_FILE
or SSL_CERT_DIR
directly in settings specific environments.
For example:
"environment.sslCertFile": "/path/to/mycert.pem"
Why it’s needed:
- MCP servers fail with SSL errors unless launched with custom cert paths
- Cursor don’t automatically respect system keychains or root stores, especially for self-signed certs
- Current workaround (launching with env vars) is not practical or scalable
Question:
If this is already possible in some way (e.g., via an undocumented setting or extension mechanism), I’d love to hear about it — couldn’t find anything solid in the docs or issues so far.
Thanks for considering this feature!