travis-mcp
Related Servers
Alternatives to travis-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to explore a JetBrains TeamCity server through 29 strictly read-only tools covering projects, build configurations, build history and dependency chains, logs, test results, failure diagnostics, the queue, agents, artifacts, and VCS changes. All access is GET-only, so agents can inspect and troubleshoot CI without triggering, canceling, or modifying anything.MIT
- AlicenseNot gradedqualityCmaintenanceProvides 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.1,350 npmMIT
- AlicenseNot gradedqualityDmaintenanceRead-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 npmISC
- AlicenseBqualityCmaintenanceEnables AI coding assistants to inspect GitHub Actions CI runs, diagnose failures with failed-step summaries and filtered job logs, read per-job coverage, and view pull request checks through read-only, allowlisted access.6MIT
- AlicenseAqualityCmaintenanceExposes GitHub Actions state as four compact, read-only tools for triaging CI failures, letting agents answer why CI is red without leaving the chat.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only inspection of Depot CI failures, job logs, GitHub Actions jobs on Depot runners, and container builds through the Depot API, so agents can diagnose issues without installing the Depot CLI.75 npmMIT
TDQS
Scored across 4 tools
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.
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.
Four tools form a well-scoped, focused surface for read-only Travis CI build inspection. Each tool clearly earns its place without unnecessary redundancy.
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.