GitLab MCP server connects but tools are not exposed to Claude's context

Resolved 💬 3 comments Opened May 12, 2026 by CarterMaster Closed May 16, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Environment:

  • OS: Windows 11 Pro
  • Claude Code version: latest
  • MCP server: @modelcontextprotocol/server-gitlab (via npx)

Problem:
The GitLab MCP server shows as ✓ Connected in claude mcp list, but none of its tools appear in Claude's available tool
context. ToolSearch returns no results for "gitlab".

Steps to reproduce:

  1. Configure GitLab MCP server in ~/.claude/settings.json with a valid GITLAB_PERSONAL_ACCESS_TOKEN
  2. Start Claude Code — server shows as Connected
  3. Ask Claude to list GitLab projects — Claude cannot find any GitLab tools

Expected behavior:
GitLab MCP tools (e.g. list_projects, get_project) should be available in Claude's tool context.

Actual behavior:
No mcp__gitlab__* tools are registered. The token is valid (confirmed via direct API call). The issue is isolated to
tool registration in Claude's context.

Workaround:
Direct PowerShell call to GitLab REST API works correctly as a workaround.

What Should Happen?

GitLab MCP tools (e.g. list_projects, get_project) should be available in Claude's tool context.

Error Messages/Logs

GitLab MCP tools (e.g. list_projects, get_project) should be available in Claude's tool context.

Steps to Reproduce

  1. Configure GitLab MCP server in ~/.claude/settings.json with a valid GITLAB_PERSONAL_ACCESS_TOKEN
  2. Start Claude Code — server shows as Connected
  3. Ask Claude to list GitLab projects — Claude cannot find any GitLab tools

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.123

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗