CERN GitLab MCP Server
Related Servers
Alternatives to CERN GitLab MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server and CLI tool that allow LLMs to interact with CERN ROOT files.9125 PyPI4MIT
- FlicenseNot gradedqualityDmaintenanceMCP server enabling AI assistants to understand GitLab repositories through on-demand source code analysis using specialized AI agents.-
- AlicenseNot gradedqualityBmaintenanceMCP server for ATLAS Open Data that enables LLMs to discover, query, and retrieve public datasets and metadata from the ATLAS experiment at CERN.121 PyPI3Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server that exposes Rucio distributed data management operations as tools for LLMs. Designed for ATLAS physicists working with grid data on analysis facilities, but usable with any Rucio instance.6Apache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server that provides 25 tools for AI agents to query and modify a dependency graph, enabling impact analysis and provenance tracking for AI-assisted development.8MIT
- AlicenseAqualityBmaintenanceAn MCP server that integrates InspireHEP high-energy physics literature with LLMs. Search papers, explore citations, retrieve author metrics, and generate formatted references.9247 PyPI8AGPL 3.0
TDQS
Scored across 15 tools
Most tools target clearly distinct resources or actions, and descriptions clarify scope. A few pairs overlap by design: get_project_readme vs get_file_content, search_code vs search_lhcb_stack, and list_tags vs list_releases, though these remain understandable.
All tool names use snake_case and follow a predictable verb_noun pattern such as list_project_files, get_project_info, search_code, and list_releases. The specialized search_lhcb_stack and inspect_project still fit the convention cleanly.
Fifteen tools is within a reasonable range for a focused GitLab exploration server. Each tool covers a distinct capability, with no obvious padding or redundant operations.
The read-only exploration surface is fairly broad, covering projects, files, code search, issues search, wiki, branches, releases, and tags. However, common GitLab lifecycle operations are missing, including merge requests, pipelines, commit history, and any create/update/delete tools, which limits agents on many typical GitLab tasks.