claude-code - 💡(How to fix) Fix GitLab plugin: support configurable base URL for self-hosted instances [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54660Fetched 2026-04-30 06:39:33
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3

Fix Action

Fix / Workaround

The GitLab plugin currently hardcodes https://gitlab.com/api/v4/mcp as the MCP server URL. This means users with self-hosted GitLab instances (GitLab CE/EE) cannot use the plugin without manually patching the plugin cache file — which gets overwritten on every plugin update.

Workaround (Current)

Code Example

"pluginConfigs": {
    "gitlab@claude-plugins-official": {                                                                                                                     
      "options": {                     
        "gitlabUrl": "https://git.example.com"                                                                                                              
      }                                                  
    }  
  }
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

The GitLab plugin currently hardcodes https://gitlab.com/api/v4/mcp as the MCP server URL. This means users with self-hosted GitLab instances (GitLab CE/EE) cannot use the plugin without manually patching the plugin cache file — which gets overwritten on every plugin update.

Proposed Solution

Support a configurable base URL via pluginConfigs in settings.json:

  "pluginConfigs": {
    "gitlab@claude-plugins-official": {                                                                                                                     
      "options": {                     
        "gitlabUrl": "https://git.example.com"                                                                                                              
      }                                                  
    }  
  }

The plugin's .mcp.json would then resolve the URL from this config value instead of hardcoding gitlab.com.

Alternative Solutions

Workaround (Current)

Manually edit ~/.claude/plugins/cache/claude-plugins-official/gitlab/unknown/.mcp.json and replace the URL — but this reverts on every plugin update.

Priority

High - Significant impact on productivity

Feature Category

MCP server integration

Use Case Example

No response

Additional Context

  • Claude Code with GitLab plugin (gitlab@claude-plugins-official)
  • Self-hosted GitLab CE/EE

extent analysis

TL;DR

To fix the issue, support a configurable base URL via pluginConfigs in settings.json to allow users with self-hosted GitLab instances to use the plugin without manual patching.

Guidance

  • Modify the settings.json file to include a configurable base URL for the GitLab plugin, as shown in the proposed solution.
  • Update the plugin's .mcp.json file to resolve the URL from the config value instead of hardcoding gitlab.com.
  • Test the plugin with the updated configuration to ensure it works as expected with self-hosted GitLab instances.
  • Consider implementing a fallback or default value for users who do not configure the gitlabUrl option.

Example

"pluginConfigs": {
  "gitlab@claude-plugins-official": {
    "options": {
      "gitlabUrl": "https://git.example.com"
    }
  }
}

Notes

This solution assumes that the plugin's .mcp.json file can be updated to support a configurable URL. If this is not possible, an alternative solution may be required.

Recommendation

Apply workaround by modifying the settings.json file and updating the plugin's configuration, as this allows users with self-hosted GitLab instances to use the plugin without manual patching.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix GitLab plugin: support configurable base URL for self-hosted instances [1 participants]