Triagic + CircleCI: ticket investigations over your repositories, read-only
Read failed build logs, pipeline status, test results, flaky tests and artifacts, to tie a ticket to a CI failure. Triggering, rerunning and rolling back pipelines stay out. Triagic connects to CircleCI from the desktop app on each member's machine, with a credential you configure, and shows every call it makes while it investigates a ticket. Nothing is copied out of CircleCI.
What you can ask
- In CircleCI, which merged change touched the export job in the last two weeks?
- Find the CircleCI pull request that introduced the 240 MB file limit
- Is there an open CircleCI issue for the OOM on large CSV imports? Link it.
- Who last changed migrations/0142.sql in CircleCI, and was it reviewed?
- List CircleCI deploy keys and outside collaborators on the private repositories
What the agent can do
These are the 7 tools Triagic exposes from the CircleCI MCP server. Anything else the server lists is dropped at connect time.
- list_followed_projects
- get_build_failure_logs
- get_latest_pipeline_status
- get_job_test_results
- find_flaky_tests
- list_artifacts
- list_component_versions
Connect in three steps
- 1
Mint a read-only credential in CircleCI
Create a dedicated user or token that can only read. Personal tokens can't be scoped, so an allowlist of the log, status, test and artifact reads is the boundary.
- 2
Add it in the Triagic portal
Integrations, then Add shared data source, then CircleCI.
- Personal API token: CircleCI → User Settings → Personal API Tokens. It carries that user's full access, so mint it from a user who can see only the projects you want reachable. The user must follow those projects.
- 3
Let a desktop pick it up
Saving validates the shape of what you typed. The first desktop app to sync starts CircleCI locally and reports running or degraded with the error text.
Field-by-field setup, TLS options and the error table: CircleCI in the docs.
Read-only, by construction
Personal tokens can't be scoped, so an allowlist of the log, status, test and artifact reads is the boundary.
FAQ
- Can Triagic change anything in CircleCI?
- No. Personal tokens can't be scoped, so an allowlist of the log, status, test and artifact reads is the boundary. Give it a read-only credential as well, so the guarantee does not rest on one layer.
- What do I need to connect CircleCI?
- Personal API token. The desktop app on a member's machine starts the connection; the portal never holds a live process.
- Does CircleCI cost extra?
- No. Every connector is included in the seat price. Start a 14-day trial without a card.
Related integrations
- GitHubBrowse repositories, issues, and pull requests, read-only. Runs GitHub's official MCP server, which requires Docker.
- GitLabBrowse projects, issues, and merge requests, read-only. Works with gitlab.com and self-hosted.
- Azure DevOpsRead work items, repos, pull requests, builds and wikis in an Azure DevOps Services organization. Nothing is created, updated or queued.
- BitbucketRead repositories, pull requests, commits, pipelines and issues in Bitbucket Cloud. The server can only send GET requests.
Try it on your own CircleCI
No card. Install the desktop app, connect CircleCI read-only, and triage a real ticket this afternoon.