[Feature Request] Add SSL_VERIFY env vars to atlassian MCP server from sooperset/mcp-atlassian

[maniak26]

Problem

The atlassian MCP server from sooperset/mcp-atlassian supports JIRA_SSL_VERIFY and CONFLUENCE_SSL_VERIFY environment variables for connecting to Jira Server / Data Center instances with self-signed or corporate CA certificates.

However, these variables are not exposed in the Docker MCP catalog manifest (servers/atlassian/server.yaml), which means:

1. Users with corporate Jira/Confluence instances behind SSL inspection cannot configure the connection
2. Users are forced to manually patch the local catalog (~/.docker/mcp/catalogs/docker-mcp.yaml) after installation
3. The variables get overwritten on every Docker Desktop update

Evidence of Support

The mcp-atlassian server (sooperset/mcp-atlassian) already fully supports these environment variables:

• .env.example (lines 108-109): Documents JIRA_SSL_VERIFY and CONFLUENCE_SSL_VERIFY as Server/DC specific settings — https://github.com/sooperset/mcp-atlassian/blob/main/.env.example#L108-L109
• src/mcp_atlassian/jira/config.py (line 236): ssl_verify = is_env_ssl_verify("JIRA_SSL_VERIFY") — https://github.com/sooperset/mcp-atlassian/blob/main/src/mcp_atlassian/jira/config.py#L236
• src/mcp_atlassian/confluence/config.py (line 163): ssl_verify = is_env_ssl_verify("CONFLUENCE_SSL_VERIFY") — https://github.com/sooperset/mcp-atlassian/blob/main/src/mcp_atlassian/confluence/config.py#L163
• src/mcp_atlassian/utils/env.py (lines 38-51): is_env_ssl_verify() function that handles SSL verification settings — https://github.com/sooperset/mcp-atlassian/blob/main/src/mcp_atlassian/utils/env.py#L38-L51

Expected Behavior

The following environment variables should be configurable in the catalog manifest.

Proposed Changes

File to modify: servers/atlassian/server.yaml

1. Add to env section:

    - name: JIRA_SSL_VERIFY
      example: "true"
      value: "{{atlassian.jira.ssl_verify}}"
    - name: CONFLUENCE_SSL_VERIFY
      example: "true"
      value: "{{atlassian.confluence.ssl_verify}}"

2. Add to parameters.properties.jira.properties and parameters.properties.confluence.properties:

      ssl_verify:
        type: boolean
        description: Verify SSL certificates (set to false for self-signed/corporate CA certs)

Workaround (not ideal)

Users currently have to manually patch their local catalog:

# After every Docker Desktop update, run:
yq -i '
  .registry.atlassian.env += [
    {"name": "JIRA_SSL_VERIFY", "value": False},
    {"name": "CONFLUENCE_SSL_VERIFY", "value": False}
  ]
' ~/.docker/mcp/catalogs/docker-mcp.yaml

Additional Context

• Upstream feature: sooperset/mcp-atlassian#975 — OS native trust store support
• Related Docker issue: sooperset/mcp-atlassian#327 — Docker version cannot bypass SSL verification
• This affects enterprise environments where Jira/Confluence are deployed internally with corporate PKI certificates

[baylakmongush]

+1. This feature would be very useful

[gorttheo]

This is a good workaround, will use it

[oskok]

+1