Skip to content

[FEATURE]: Add MCP client support for skipping certificate validation #23506

Closed as not planned

Description

@wdec

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Add an optional TLS verification override to the MCP client, allowing it to skip server certificate validation for development and trusted local environments with self-signed certificates. This would align the MCP client with standard behavior available in many TLS-capable tools and clients, including curl, where certificate verification can be explicitly disabled when needed and avoid the (messy) workaround of installing special user certs, or disabling TLS validation for all clients.

Proposed opencode.json config option schema:

{                                                                                                                                                               
       "mcp": {                                                                                                              
         "my-server": {                                                                                                                                    
           "type": "remote",                                                                                                                                         
           "url": "https://my-server.local/mcp",                                                                                                      
           "insecure": true                                                                                                                 
         }                                                                                                                                       
       }                                                                                                                                               
}   

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Apr 20, 2026
  2. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on Apr 20, 2026
  3. removed
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on May 3, 2026
  4. sklakegg commented on Jun 3, 2026

    @sklakegg

    Would be great!

  5. karup commented on Aug 2, 2026

    @karup

    I created a duplicate to this #40111.
    Apology in advance but I needed to add more details

  6. github-actions commented on Oct 1, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions