Skip to content

fix handling of mcp remote#303

Merged
peterj merged 6 commits intoagentregistry-dev:mainfrom
christian-posta:ceposta-mcp-remote
Mar 10, 2026
Merged

fix handling of mcp remote#303
peterj merged 6 commits intoagentregistry-dev:mainfrom
christian-posta:ceposta-mcp-remote

Conversation

@christian-posta
Copy link
Copy Markdown
Contributor

@christian-posta christian-posta commented Mar 6, 2026

Description

handle remote MCP servers

Change Type

/kind feature
/kind fix

Changelog

handle remote MCP servers

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adjusts the MCP CLI publish flow to distinguish “remote-only” MCP servers (already deployed endpoints) from package-based servers, aligning the published ServerJSON shape with how the registry models remotes vs installable packages.

Changes:

  • Adds --remote-url to publish an already-deployed MCP server as a remotes[] entry (no packages[]).
  • Updates mcp publish help text/examples and shifts required flag validation to be mode-dependent.
  • Adds .claude to .gitignore.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 5 comments.

File Description
internal/cli/mcp/publish.go Introduces remote-only publish mode and constructs ServerJSON with Remotes instead of Packages.
.gitignore Ignores .claude IDE/tooling artifacts.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

christian-posta and others added 2 commits March 9, 2026 11:02
- Fix --transport flag help text to reflect mode-dependent valid values
- Fix --transport-url help text (revert erroneous "used with --type")
- Update remote publish example to use reverse-DNS namespace format
- Add mutual exclusivity check: error when --type/--package-id used with --remote-url
- Add unit tests for buildRemoteServerJSON and remote transport validation
- Add Scheme field to RemoteMCPServer and SSETargetSpec so https:// URLs
  are preserved through the publish -> registry -> deploy pipeline instead
  of being hardcoded to http://
- Update parseUrl, kagent translator (buildRemoteMCPURL), and docker-compose
  translator to propagate the scheme end-to-end
- Add e2e tests for --remote-url publish flow including URL preservation,
  dry-run output, and flag conflict validation
peterj added 3 commits March 9, 2026 14:33
Signed-off-by: Peter Jausovec <[email protected]>
Signed-off-by: Peter Jausovec <[email protected]>
Signed-off-by: Peter Jausovec <[email protected]>
@peterj peterj added this pull request to the merge queue Mar 9, 2026
Merged via the queue into agentregistry-dev:main with commit 09a6e9b Mar 10, 2026
7 checks passed
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.

3 participants