Circleci Automation

1---
2name: circleci-automation
3description: "Automate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata. Always search tools first for current schemas."
4requires:
5  mcp: [rube]
6---
7 
8# CircleCI Automation via Rube MCP
9 
10Automate CircleCI CI/CD operations through Composio's CircleCI toolkit via Rube MCP.
11 
12## Prerequisites
13 
14- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
15- Active CircleCI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `circleci`
16- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
17 
18## Setup
19 
20**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
21 
22 
231. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
242. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `circleci`
253. If connection is not ACTIVE, follow the returned auth link to complete CircleCI authentication
264. Confirm connection status shows ACTIVE before running any workflows
27 
28## Core Workflows
29 
30### 1. Trigger a Pipeline
31 
32**When to use**: User wants to start a new CI/CD pipeline run
33 
34**Tool sequence**:
351. `CIRCLECI_TRIGGER_PIPELINE` - Trigger a new pipeline on a project [Required]
362. `CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID` - Monitor resulting workflows [Optional]
37 
38**Key parameters**:
39- `project_slug`: Project identifier in format `gh/org/repo` or `bb/org/repo`
40- `branch`: Git branch to run the pipeline on
41- `tag`: Git tag to run the pipeline on (mutually exclusive with branch)
42- `parameters`: Pipeline parameter key-value pairs
43 
44**Pitfalls**:
45- `project_slug` format is `{vcs}/{org}/{repo}` (e.g., `gh/myorg/myrepo`)
46- `branch` and `tag` are mutually exclusive; providing both causes an error
47- Pipeline parameters must match those defined in `.circleci/config.yml`
48- Triggering returns a pipeline ID; workflows start asynchronously
49 
50### 2. Monitor Pipelines and Workflows
51 
52**When to use**: User wants to check the status of pipelines or workflows
53 
54**Tool sequence**:
551. `CIRCLECI_LIST_PIPELINES_FOR_PROJECT` - List recent pipelines for a project [Required]
562. `CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID` - List workflows within a pipeline [Required]
573. `CIRCLECI_GET_PIPELINE_CONFIG` - View the pipeline configuration used [Optional]
58 
59**Key parameters**:
60- `project_slug`: Project identifier in `{vcs}/{org}/{repo}` format
61- `pipeline_id`: UUID of a specific pipeline
62- `branch`: Filter pipelines by branch name
63- `page_token`: Pagination cursor for next page of results
64 
65**Pitfalls**:
66- Pipeline IDs are UUIDs, not numeric IDs
67- Workflows inherit the pipeline ID; a single pipeline can have multiple workflows
68- Workflow states include: success, running, not_run, failed, error, failing, on_hold, canceled, unauthorized
69- `page_token` is returned in responses for pagination; continue until absent
70 
71### 3. Inspect Job Details
72 
73**When to use**: User wants to drill into a specific job's execution details
74 
75**Tool sequence**:
761. `CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID` - Find workflow containing the job [Prerequisite]
772. `CIRCLECI_GET_JOB_DETAILS` - Get detailed job information [Required]
78 
79**Key parameters**:
80- `project_slug`: Project identifier
81- `job_number`: Numeric job number (not UUID)
82 
83**Pitfalls**:
84- Job numbers are integers, not UUIDs (unlike pipeline and workflow IDs)
85- Job details include executor type, parallelism, start/stop times, and status
86- Job statuses: success, running, not_run, failed, retried, timedout, infrastructure_fail, canceled
87 
88### 4. Retrieve Build Artifacts
89 
90**When to use**: User wants to download or list artifacts produced by a job
91 
92**Tool sequence**:
931. `CIRCLECI_GET_JOB_DETAILS` - Confirm job completed successfully [Prerequisite]
942. `CIRCLECI_GET_JOB_ARTIFACTS` - List all artifacts from the job [Required]
95 
96**Key parameters**:
97- `project_slug`: Project identifier
98- `job_number`: Numeric job number
99 
100**Pitfalls**:
101- Artifacts are only available after job completion
102- Each artifact has a `path` and `url` for download
103- Artifact URLs may require authentication headers to download
104- Large artifacts may have download size limits
105 
106### 5. Review Test Results
107 
108**When to use**: User wants to check test outcomes for a specific job
109 
110**Tool sequence**:
1111. `CIRCLECI_GET_JOB_DETAILS` - Verify job ran tests [Prerequisite]
1122. `CIRCLECI_GET_TEST_METADATA` - Retrieve test results and metadata [Required]
113 
114**Key parameters**:
115- `project_slug`: Project identifier
116- `job_number`: Numeric job number
117 
118**Pitfalls**:
119- Test metadata requires the job to have uploaded test results (JUnit XML format)
120- If no test results were uploaded, the response will be empty
121- Test metadata includes classname, name, result, message, and run_time fields
122- Failed tests include failure messages in the `message` field
123 
124## Common Patterns
125 
126### Project Slug Format
127 
128```
129Format: {vcs_type}/{org_name}/{repo_name}
130- GitHub:    gh/myorg/myrepo
131- Bitbucket: bb/myorg/myrepo
132```
133 
134### Pipeline -> Workflow -> Job Hierarchy
135 
136```
1371. Call CIRCLECI_LIST_PIPELINES_FOR_PROJECT to get pipeline IDs
1382. Call CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID with pipeline_id
1393. Extract job numbers from workflow details
1404. Call CIRCLECI_GET_JOB_DETAILS with job_number
141```
142 
143### Pagination
144 
145- Check response for `next_page_token` field
146- Pass token as `page_token` in next request
147- Continue until `next_page_token` is absent or null
148 
149## Known Pitfalls
150 
151**ID Formats**:
152- Pipeline IDs: UUIDs (e.g., `5034460f-c7c4-4c43-9457-de07e2029e7b`)
153- Workflow IDs: UUIDs
154- Job numbers: Integers (e.g., `123`)
155- Do NOT mix up UUIDs and integers between different endpoints
156 
157**Project Slugs**:
158- Must include VCS prefix: `gh/` for GitHub, `bb/` for Bitbucket
159- Organization and repo names are case-sensitive
160- Incorrect slug format causes 404 errors
161 
162**Rate Limits**:
163- CircleCI API has per-endpoint rate limits
164- Implement exponential backoff on 429 responses
165- Avoid rapid polling; use reasonable intervals (5-10 seconds)
166 
167## Quick Reference
168 
169| Task | Tool Slug | Key Params |
170|------|-----------|------------|
171| Trigger pipeline | CIRCLECI_TRIGGER_PIPELINE | project_slug, branch, parameters |
172| List pipelines | CIRCLECI_LIST_PIPELINES_FOR_PROJECT | project_slug, branch |
173| List workflows | CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID | pipeline_id |
174| Get pipeline config | CIRCLECI_GET_PIPELINE_CONFIG | pipeline_id |
175| Get job details | CIRCLECI_GET_JOB_DETAILS | project_slug, job_number |
176| Get job artifacts | CIRCLECI_GET_JOB_ARTIFACTS | project_slug, job_number |
177| Get test metadata | CIRCLECI_GET_TEST_METADATA | project_slug, job_number |
178