Skip to content

Feature: Allow HTTP for self-hosted Sentry instances in isolated networks #891

@MaximZemskov

Description

@MaximZemskov

Problem

The stdio server hardcodes https:// when constructing API and web URLs from the --host flag. See
packages/mcp-core/src/api-client/client.ts#L176

this.apiPrefix = `https://${host}/api/0`;

This makes the package unusable for self-hosted Sentry instances that live on internal networks reachable only through VPN and don't have TLS configured.

Proposal

Add an opt-in --insecure-http flag that switches the scheme to http://.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions