Default HTTPS redirection for remote MCP server with opt-out env var.#1169
Merged
kvenkatrajan merged 1 commit intomainfrom Nov 14, 2025
Merged
Default HTTPS redirection for remote MCP server with opt-out env var.#1169kvenkatrajan merged 1 commit intomainfrom
kvenkatrajan merged 1 commit intomainfrom
Conversation
vukelich
requested review from
KarishmaGhiya,
alzimmermsft,
chidozieononiwu,
hallipr,
msalaman,
wbreza and
weshaggard
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds default HTTPS redirection to the remote MCP server with an opt-out mechanism via the AZURE_MCP_DISABLE_HTTPS_REDIRECTION environment variable. This enhances security by ensuring HTTPS is used by default unless explicitly disabled.
Key Changes:
- Added HTTPS redirection middleware in
CreateHttpHost()that activates by default - Introduced
AZURE_MCP_DISABLE_HTTPS_REDIRECTIONenvironment variable to allow opt-out for scenarios like reverse proxy deployments or local development
kvenkatrajan
approved these changes
Nov 13, 2025
anuchandy
approved these changes
Nov 13, 2025
JasonYeMSFT
approved these changes
Nov 13, 2025
github-project-automation
Bot
moved this from Untriaged
to In Progress
in Azure MCP Server
anuchandy
approved these changes
Nov 14, 2025
vukelich
force-pushed
the
users/vukelich/httpsredirect
branch
from
a7e58ba to
5aa7704
Compare
anuchandy
approved these changes
Nov 14, 2025
colbytimm
pushed a commit
to colbytimm/microsoft-mcp
that referenced
this pull request
Dec 8, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
[Provide a clear, concise description of the changes]Use
app.UseHttpsRedirection()within the remote MCP server middleware unless opt-ed out withAZURE_MCP_DANGEROUSLY_DISABLE_HTTPS_REDIRECTION[Any additional context, screenshots, or information that helps reviewers]GitHub issue number?
[Link to the GitHub issue this PR addresses]Pre-merge Checklist
servers/Azure.Mcp.Server/CHANGELOG.mdand/orservers/Fabric.Mcp.Server/CHANGELOG.mdfor product changes (features, bug fixes, UI/UX, updated dependencies)servers/Azure.Mcp.Server/README.mdand/orservers/Fabric.Mcp.Server/README.mddocumentationeng/scripts/Process-PackageReadMe.ps1. See Package README/servers/Azure.Mcp.Server/docs/azmcp-commands.mdand/or/docs/fabric-commands.md.\eng\scripts\Update-AzCommandsMetadata.ps1to update tool metadata in azmcp-commands.md (required for CI)ToolDescriptionEvaluatorand obtained a score of0.4or more and a top 3 ranking for all related test prompts/servers/Azure.Mcp.Server/docs/e2eTestPrompts.mdcrypto mining, spam, data exfiltration, etc.)/azp run mcp - pullrequest - liveto run Live Test Pipeline