Skip to content

[MCP] Fix connection string for on-prem environments#6727

Open
onbuyuka wants to merge 1 commit intomainfrom
bugs/622243-MCPOnPremConnString
Open

[MCP] Fix connection string for on-prem environments#6727
onbuyuka wants to merge 1 commit intomainfrom
bugs/622243-MCPOnPremConnString

Conversation

@onbuyuka
Copy link
Contributor

@onbuyuka onbuyuka commented Feb 18, 2026

Summary

Fix MCP connection string showing incorrect data for on-premises deployments.

Problem

When generating an MCP connection string on an on-premises BC instance:

  • The URL was a hardcoded SaaS URL instead of the actual server URL
  • TenantId and EnvironmentName headers were included, which don't apply on-prem

Changes

  • Detect SaaS vs on-prem via EnvironmentInformation.IsSaaS()
  • On-prem: Derive MCP URL from GetUrl(ClientType::Api), strip the /api suffix, and append /mcp to produce the correct URL (e.g. http://server:7047/instance/mcp)
  • On-prem: Omit TenantId and EnvironmentName headers from the connection string
  • SaaS: Keep existing TIE/Prod URL logic and all headers unchanged
  • Add test validating on-prem connection string format
  • Expose GenerateConnectionString in test library

Fixes AB#622243

- Detect SaaS vs on-prem via EnvironmentInformation.IsSaaS()
- On-prem: derive MCP URL from GetUrl(ClientType::Api) stripping /api suffix, append /mcp
- On-prem: omit TenantId and EnvironmentName headers from connection string
- SaaS: keep existing TIE/Prod URL and all headers
- Add test for on-prem connection string generation
- Expose GenerateConnectionString in test library
@onbuyuka onbuyuka requested a review from a team as a code owner February 18, 2026 11:57
@github-actions github-actions bot added this to the Version 28.0 milestone Feb 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments