Skip to main content
Glama
vlhommeau

travis-mcp

by vlhommeau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to travis-mcp

No user-submitted related servers found.

    Related Servers

    • jenkins-mcp

      ruslan-casafari
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to Jenkins, enabling users to inspect project and environment build status, list builds, retrieve console logs and test reports, diagnose failed builds, and search jobs via natural language, without triggering or changing builds.
      408 npm
      MIT

    • Jenkins MCP Server

      ooooshino
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server for Jenkins CI, enabling AI agents to securely query job/build status, logs, artifacts, and generate verification reports for loop workflows.
      17 npm
      ISC

    • DevOps MCP Server

      huangjien
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only integration with GitHub, Jenkins, and Artifactory for DevOps monitoring, analysis, and troubleshooting. Provides repository inspection, build log retrieval, and artifact management through natural language.
      MIT

    • OPP Observatory MCP

      OPP-studio-macchino
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only production observability through a small set of tools for health, job status, latest data, approved logs, and deployment metadata, enabling AI planning and review without a production write path.
      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

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct layer of the CI data model: build, jobs of a build, build list, and job log. There is no overlap or ambiguity in purpose.

    Naming Consistency5/5

    All names follow a clean snake_case verb_noun pattern. The use of list_ for the plural build listing and get_ for singular resources is a standard and predictable convention.

    Tool Count5/5

    Four tools form a well-scoped, focused surface for read-only Travis CI build inspection. Each tool clearly earns its place without unnecessary redundancy.

    Completeness4/5

    The set covers the complete inspection workflow: discover builds, view build details, drill into jobs, and fetch job logs. Missing write operations like restart or cancel are likely out of scope but could be considered minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources