Skip to main content
Glama
cbyrohl

cdash-mcp

by cbyrohl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CDASH_URLNoCDash instance URLhttps://my.cdash.org
CDASH_TOKENNoBearer token for authentication (required for private instances)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_dashboardA

Get the CDash dashboard for a project, showing build groups and status.

Args:
    project: CDash project name (e.g. "PublicDashboard").
    date: Optional date (YYYY-MM-DD). Defaults to today.
get_failing_testsA

Find non-passing tests across all builds for a project. Most useful for CI triage.

Args:
    project: CDash project name (e.g. "PublicDashboard").
    date: Optional date (YYYY-MM-DD). Defaults to today.
    test_name: Optional filter to match test names containing this string.
    limit: Maximum number of tests to return (default 50, max 200).
    offset: Number of tests to skip (default 0). Use for pagination.
get_build_detailsB

Get detailed information about a specific build, including configure/compile/test summaries.

Args:
    build_id: The CDash build ID.
get_build_errorsA

View compiler errors or warnings for a build, with source file and line info.

Args:
    build_id: The CDash build ID.
    warnings: If True, show warnings instead of errors.
    limit: Maximum number of errors to return (default 30, max 200).
    offset: Number of errors to skip (default 0). Use for pagination.
get_build_testsB

List tests for a specific build, optionally filtered by status.

Args:
    build_id: The CDash build ID.
    status_filter: Optional filter: "passed", "failed", or "notrun".
    limit: Maximum number of tests to return (default 50, max 200).
    offset: Number of tests to skip (default 0). Use for pagination.
get_configure_outputA

View CMake configure command and output for a build.

Args:
    build_id: The CDash build ID.
    output_offset: Character offset into the configure output (default 0).
    output_limit: Maximum characters of output to return (default 34816 = 34 KB).
        Set to 0 for no limit.
get_test_summaryA

Get summary of a test across builds — shows pass/fail history to detect flaky tests.

Args:
    project: CDash project name (e.g. "PublicDashboard").
    test_name: Exact name of the test.
    date: Optional date (YYYY-MM-DD). Defaults to today.
    limit: Maximum number of builds to return (default 50, max 200).
    offset: Number of builds to skip (default 0). Use for pagination.
get_build_updateB

View source code changes (VCS commits) associated with a build.

Args:
    build_id: The CDash build ID.
get_project_overviewA

Get project overview with aggregate build/test/coverage statistics.

Args:
    project: CDash project name (e.g. "PublicDashboard").
    date: Optional date (YYYY-MM-DD). Defaults to today.
get_coverage_comparisonA

Compare code coverage across builds for a project. Useful for detecting coverage regressions.

Args:
    project: CDash project name (e.g. "PublicDashboard").
    date: Optional date (YYYY-MM-DD). Defaults to today.
    build_id: Optional build ID to get coverage for a specific build.
        Recommended: provide a build_id from the dashboard for reliable results.
        Without build_id, uses cross-build comparison (only works for Nightly builds).
    limit: Maximum number of files to return (default 50, max 200).
    offset: Number of files to skip (default 0). Use for pagination.
get_dynamic_analysisA

Get dynamic analysis results (e.g. Valgrind, sanitizers) for a build.

Args:
    build_id: The CDash build ID.
    limit: Maximum number of defect entries to return (default 50, max 200).
    offset: Number of defect entries to skip (default 0). Use for pagination.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.9/5.0

Scored across 11 tools

Disambiguation4/5

Most tools are clearly separated by resource type, such as build details, errors, tests, coverage, and dynamic analysis. However, get_dashboard and get_project_overview both provide project-level aggregate status, and get_failing_tests overlaps somewhat with get_build_tests with a failure filter, creating minor ambiguity.

Naming Consistency5/5

All tools follow the get_<resource> pattern consistently, making the set highly predictable. The names clearly indicate both the action (get) and the target (dashboard, build, coverage, tests, etc.).

Tool Count5/5

With 11 tools, the count is well within the ideal range for a domain-specific read-only CDash server. Each tool covers a meaningful slice of the dashboard/build/test/coverage surface without unnecessary duplication.

Completeness4/5

The tool set covers the main CDash read workflows: dashboards, build details, test results, errors, coverage, dynamic analysis, configure output, and VCS update info. The main gap is project discovery—there is no way to list available projects, so agents must already know the project name.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources