Skip to main content
Glama
Sign In
CERN ROOT MCP Server

CERN ROOT MCP Server

by MohamedElashri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to CERN ROOT MCP Server

No user-submitted related servers found.

    Related Servers

    • rucio-mcp

      kratsg
      A
      license
      Not graded
      quality
      C
      maintenance
      An 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.
      6
      Apache 2.0

    • XRootD MCP Server

      eic
      A
      license
      A
      quality
      B
      maintenance
      An MCP server providing access to XRootD file systems, allowing LLMs to browse directories, read file metadata, and access contents via the root:// protocol. It supports advanced features like campaign discovery, file searching, and ROOT file analysis for scientific data management.
      18
      1
      MIT

    • CERN GitLab MCP Server

      MohamedElashri
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that connects LLMs to CERN GitLab to discover and analyze High Energy Physics code, documentation, and analysis examples. It provides 14 tools for repository browsing, dependency parsing, and CI/CD configuration analysis.
      15
      54 PyPI
      4
      AGPL 3.0

    • mcp-cli-catalog

      abcpro1
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that publishes CLI tools on your machine for discoverability by LLMs
      7 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct stage of ROOT file analysis: discovery (list_files), structure inspection (inspect_file), branch listing, validation, reading, statistics, export, and server metadata/mode control. Overlap between inspect_file and list_branches is clarified by descriptions focusing on file structure versus TTree/RNTuple branches.

    Naming Consistency5/5

    All names use snake_case with verb_noun structure (list_files, inspect_file, read_branches, get_branch_stats, export_data, get_server_info). switch_mode fits the verb_noun convention despite being administrative rather than analytical.

    Tool Count5/5

    Nine tools is well-scoped for a read-only ROOT analysis server, covering discovery through export without redundant operations. Each tool has a clear, non-overlapping role in the workflow.

    Completeness3/5

    The surface covers discovery, inspection, validation, reading, statistics, and export, but references histograms as an alternative in tool descriptions without providing any histogram or plotting tool. This creates a notable dead end for a core ROOT analysis operation, though agents can partially work around it via stats and export.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources