Travis CI MCP server

What the model can do

Travis CI builds: repositories and whether Travis is active on them, builds with state, branch or tag, short commit, pull request, trigger (push, pull request, cron, API) and duration, a build's jobs and stages, build requests and why they were or were not built, branches with their last build, and cron schedules. Logs, commit authors and commit messages are never read. When you ask, can trigger a build on a branch, restart or cancel a build or job, add or delete a branch cron, and activate or deactivate a repository.

Reads

• travisci_list_reposTravis CI repositories this token can see: id, slug, whether Travis is active on it, private, default branch and description.
• travisci_list_buildsTravis CI builds, newest first: id, number, state (created, started, passed, failed, errored, canceled), previous state, trigger, branch or tag…
• travisci_get_buildOne Travis CI build with its jobs (id, number, state, stage, queue, allowed to fail, timings).
• travisci_get_jobOne Travis CI job: number, state, stage, queue, whether it may fail, its build and timings.
• travisci_list_requestsBuild requests of a Travis CI repository, newest first: id, state, result (approved or rejected), why it was or was not built, trigger, branch, when…
• travisci_list_branchesBranches of a Travis CI repository, the default first: name, whether it still exists on the code host, and its last build's id, number and state.
• travisci_list_cronsCron builds of a Travis CI repository: id, branch, interval (daily, weekly, monthly), whether it skips when a recent build exists, last and next run.

Acts, when you ask

These change something in Travis CI. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• travisci_trigger_buildAsks Travis CI to build a repository's branch now (POST requests), at its latest commit or the sha given…
• travisci_restart_buildRestarts a finished or canceled Travis CI build, running all its jobs again.
• travisci_cancel_buildCancels a running Travis CI build and its jobs (state canceled); it cannot be resumed, only restarted.
• travisci_restart_jobRestarts one finished or canceled Travis CI job.
• travisci_cancel_jobCancels one running Travis CI job; it cannot be resumed, only restarted.
• travisci_create_cronAdds a cron to a Travis CI repository's branch that builds it daily, weekly or monthly, each run spending credits…
• travisci_delete_cronDeletes a Travis CI cron, so its branch stops building on a schedule.
• travisci_activate_repoActivates a repository on Travis CI, so its pushes and pull requests start building (and spending credits).
• travisci_deactivate_repoDeactivates a repository on Travis CI, so nothing builds on it until reactivated (its crons and history stay).

Connect it

First connect Travis CI on Dashboard → Connections, then add Memtro to your client once. The Travis CI tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Travis CI connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which builds failed on main this week?
• › Which job broke in the last build of the api repository?
• › Why did yesterday's push to the release branch not build?
• › When does the cron on main run next?
• › Restart the last failed build on main.

Questions

Is this an official Travis CI MCP server?

No. It is Memtro's MCP server with Memtro's Travis CI connector behind it: the connector reads Travis CI through its API with the credentials you connect on Dashboard → Connections, and Travis CI publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Travis CI?

Only when you ask, and only what it has been granted: trigger a build of a repository's branch, optionally at a commit or with config overrides (spends credits); restart a finished or canceled build (spends credits); cancel a running build; restart a job (spends credits); cancel a running job; add a daily, weekly or monthly cron build on a branch; delete a cron; activate a repository on Travis CI; deactivate a repository on Travis CI. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server