travis-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRAVIS_API_URL | No | Base URL for the Travis CI API v3. | https://api.travis-ci.com |
| TRAVIS_WEB_URL | No | Base URL for the Travis CI web interface. | https://app.travis-ci.com |
| TRAVIS_API_TOKEN | Yes | Travis CI API token. Get it from https://app.travis-ci.com/account/preferences → API authentication, or with `travis login --pro && travis token --pro`. | |
| TRAVIS_DEFAULT_REPO | No | Default repository in `owner/name` format, used when `list_builds` gets no `repo` argument. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_buildB | State, branch/PR, commit, timing and job IDs of one Travis build. |
| get_build_jobsA | Jobs of one Travis build with their state and stage, to find which job failed. |
| list_buildsA | Most recent builds of a repository, newest first. Filter by branch, event type, state or pull request number. |
| get_job_logA | Plain-text log of one Travis job, ANSI codes stripped. Returns the last lines by default; use grep to extract matching lines with context instead. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.