Add develop-mcp list-published-servers command - #504
Open
deepaligargms wants to merge 2 commits into
Open
deepaligargms wants to merge 2 commits into
deepaligargms wants to merge 2 commits into
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Contributor
There was a problem hiding this comment.
Copilot review overview
🔵 Needs a closer look
The production endpoint is not deployed, and the new HTTP integration lacks service-level request and response tests.
Review effort: Balanced
Findings: 1
Open (1)
What changed in this PR
Adds tenant-wide discovery of published MCP servers, including approval status and source environment.
Changes:
- Adds the
list-published-serversCLI command and platform API integration. - Introduces response models and command/model tests.
- Updates command documentation and release notes.
| File | Description |
|---|---|
CHANGELOG.md |
Adds the feature release note. |
docs/commands/README.md |
Links the new command reference. |
src/DEVELOPER.md |
Documents usage for developers. |
Commands/DevelopMcpCommand.cs |
Registers and implements the command. |
Models/PublishedMcpServer.cs |
Defines published-server response models. |
Models/README.md |
Catalogs the new model. |
Services/Agent365ToolingService.cs |
Calls the published-servers endpoint. |
Services/IAgent365ToolingService.cs |
Exposes the new service operation. |
Commands/DevelopMcpCommandRegressionTests.cs |
Tests output, failure, empty, and dry-run paths. |
Commands/DevelopMcpCommandTests.cs |
Tests command registration and options. |
Models/PublishedMcpServersResponseTests.cs |
Tests response deserialization. |
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| } | ||
|
|
||
| /// <inheritdoc /> | ||
| public async Task<PublishedMcpServersResponse?> ListPublishedServersAsync(CancellationToken cancellationToken = default) |
Response is now { servers } with mcpServerName, status, sourceMcpServerName and
sourceEnvironmentId (MCP-Platform PR 3968 review).
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Comment on lines
+411
to
+414
| logger.LogInformation("{McpServerName}", server.McpServerName ?? "Unknown"); | ||
| logger.LogInformation(" Status: {Status}", server.Status ?? "Unknown"); | ||
| logger.LogInformation(" Source MCP Server Name: {SourceMcpServerName}", server.SourceMcpServerName ?? "Unknown"); | ||
| logger.LogInformation(" Source Environment ID: {SourceEnvironmentId}", server.SourceEnvironmentId ?? "Unknown"); |
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.

Add develop-mcp list-published-servers command
Summary
Adds
a365 develop-mcp list-published-servers, which lists every MCP server published to tenant scope from the Dataverse environments the caller can access, with each server's approval status, in one call.Why
list-servers -e <env>shows one environment's Dataverse servers, not what is published to the tenant. To answer "what have I published, and is it approved?" you had to run it once per environment, and it still didn't show the tenant URL or approval status.Behavior
list-servers(AgentTools.ListMCPServers.All), so no new consent is needed.PendingApproval,Approved, orBlocked. Description is printed only when the server has one.--dry-runmakes no calls.Testing
serversarray.Notes for reviewers
list-serversexits 0 when its service call fails, which breaks the exit-code rule. Happy to fix it separately.#develop-mcp-list-published-serversindocs/commands/README.mdlands at the top of the page until the Learn reference is updated.