microsoft / microsoft/BCApps

Expose GenerateConnectionString and ShowConnectionString procedures to the public MCP Config API

Open
#11,343 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Approved request-for-external Team: Integrations
Dominant language
AL
Stars
683
Forks
459
Avg merge
3d 26m
Merged PRs (30d)
633

Description

Why do you need this change?

In an ISV product, we are creating an assisted setup experience to quickly create predefined MCP Configurations for customers. The assisted setup guides users through Rapidly setting up multiple APIs and tools into an MCP Configuration instead of manual configuring them, providing a fast way to get started with the MCP server.

Current limitation: The GenerateConnectionString and ShowConnectionString procedures are currently locked behind the internal "MCP Config Implementation" codeunit (8351). These procedures are essential for our assisted setup workflow because:

After the customer completes the assisted setup and we programmatically create the MCP Configuration, we need to generate the connection string for that configuration
We need to display the connection string directly within the assisted setup UI (or immediately after completion) so customers can copy and use the MCP Connection String to connect to other applications
Currently, there is no public API method to retrieve the connection string, forcing workarounds or duplicate implementations

Benefit: Exposing these two procedures as public API methods in the "MCP Config" codeunit (8350) will:

  1. Enable ISV partners to create streamlined assisted setup experiences
    2.Allow programmatic access to generated connection strings
Describe the request

Procedures to Expose

  1. GenerateConnectionString

Current location: MCPConfigImplementation Codeunit 8351 (internal)
Current signature: internal procedure GenerateConnectionString(ConfigurationName: Text[100]): Text
Proposed public signature: Should be wrapped in MCPConfig Codeunit 8350 as a public procedure
Purpose: Generates the connection string JSON for a specified MCP configuration, handling both SaaS and on-premises environments, with proper encoding for non-ASCII characters in company and configuration names

  1. ShowConnectionString

Current location: MCPConfigImplementation Codeunit 8351 (internal)
Current signature: internal procedure ShowConnectionString(ConfigurationName: Text[100])
Proposed public signature: Should be wrapped in MCPConfig Codeunit 8350 as a public procedure
Purpose: Opens a modal dialog displaying the connection string for a configuration, allowing end-users to view and copy the string

Provide an implementation (optional)
  • I will provide the implementation for this extensibility request

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the MCP Config codeunit 8350 and the internal MCP Config Implementation codeunit 8351, focusing on the existing GenerateConnectionString and ShowConnectionString procedures. Expose the requested procedures through codeunit 8350 while preserving their stated SaaS, on-premises, encoding, and display behavior; verify that assisted setup code can call them and that the connection string is generated or shown as intended.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend-api-design
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.