Description
Current behavior
When the MCP server calls list_repositories for a given component, it uses gitlab.com as a hard-coded Git server URL.
Impact
This prevents the MCP server from being used with any Git server implementation other than gitlab.com (e.g., self-hosted GitLab instances, GitHub, Bitbucket, etc.), limiting its usability in environments that rely on alternative or on-premise Git hosting.
Expected behaviour
The Git server should be configurable (e.g., via environment variable, config file, or component metadata) rather than hard-coded, so list_repositories can work correctly against any supported Git server.
Suggested fix
Replace the hard-coded gitlab.com reference with a configurable value, sourced from existing connection/config settings if available.
Description
Current behavior
When the MCP server calls list_repositories for a given component, it uses gitlab.com as a hard-coded Git server URL.
Impact
This prevents the MCP server from being used with any Git server implementation other than gitlab.com (e.g., self-hosted GitLab instances, GitHub, Bitbucket, etc.), limiting its usability in environments that rely on alternative or on-premise Git hosting.
Expected behaviour
The Git server should be configurable (e.g., via environment variable, config file, or component metadata) rather than hard-coded, so list_repositories can work correctly against any supported Git server.
Suggested fix
Replace the hard-coded gitlab.com reference with a configurable value, sourced from existing connection/config settings if available.