A
licenseB
qualityC
maintenanceAn MCP server and CLI tool that allow LLMs to interact with CERN ROOT files.
9
3
MIT
CERN GitLab MCP Server
Related Servers
Alternatives to CERN GitLab MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server enabling AI assistants to understand GitLab repositories through on-demand source code analysis using specialized AI agents.-
- AlicenseNot gradedqualityDmaintenanceMCP server for ATLAS Open Data that enables LLMs to discover, query, and retrieve public datasets and metadata from the ATLAS experiment at CERN.2Apache 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.42 PyPI6Apache 2.0
- AlicenseNot gradedqualityAmaintenanceMCP 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
- AlicenseAqualityAmaintenanceAn MCP server that integrates InspireHEP high-energy physics literature with LLMs. Search papers, explore citations, retrieve author metrics, and generate formatted references.97AGPL 3.0
TDQS
A4/5.0
Scored across 15 tools
Disambiguation5/5
Each tool targets a distinct resource or action: projects, files, code, issues, wiki, releases, branches, tags, and connectivity. Even the multiple search tools are clearly separated by search surface (projects, global code, LHCb stack, issues). The only mild overlap is between get_file_content and get_project_readme, but the README tool's auto-detection makes it a clearly specialized convenience function.
Naming Consistency5/5
Tool names consistently follow a verb_noun snake_case pattern: get_, list_, search_, test_connectivity, and inspect_project. Verbs are predictable by action type, and no naming convention mixing or irregular casing is present.
Tool Count4/5
At 15 tools, the set sits at the upper boundary of the ideal range, but each tool still earns a place given the breadth of read-only GitLab exploration. It is slightly heavy, especially with niche additions like search_lhcb_stack, but not bloated or redundant.
Completeness4/5
The tool surface covers project discovery, file browsing, code search, issues, wiki, releases, branches, tags, and project inspection, which forms a strong read-oriented workflow. Missing merge requests, commit history, and diff access are notable gaps for full GitLab coverage, but they are outside the apparent exploration-focused scope.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive