circleci-automation
πPluginAutomates CircleCI CI/CD operations through Composio's Rube MCP, including pipeline triggering, workflow monitoring, and artifact retrieval.
Installation
This repo has no plugin marketplace file at its root, so /plugin cannot add it. See the README for how to install it.
What this plugin does
Overview
CircleCI Automation is a Claude Code plugin that automates CI/CD operations through Composio's Rube MCP. It triggers pipelines, monitors workflows, and retrieves build artifacts directly from Claude Code.
Key Features
- Triggers pipelines with CIRCLECI_TRIGGER_PIPELINE and monitors status with CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID
- Retrieves build artifacts and test results for automated analysis
- Manages pipeline configurations and environment variables through the CircleCI API
Who is this for?
Developers using CircleCI for CI/CD who want to trigger and monitor builds without leaving Claude Code.
Summarized by AI from this repo's README. Suggest a better one
README.md
View on GitHub βAutomate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata. Always search tools first for current schemas.
CircleCI Automation via Rube MCP
Automate CircleCI CI/CD operations through Composio's CircleCI toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/circleci
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active CircleCI connection via
RUBE_MANAGE_CONNECTIONSwith toolkitcircleci - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitcircleci - If connection is not ACTIVE, follow the returned auth link to complete CircleCI authentication
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Trigger a Pipeline
When to use: User wants to start a new CI/CD pipeline run
Tool sequence:
CIRCLECI_TRIGGER_PIPELINE- Trigger a new pipeline on a project [Required]CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID- Monitor resulting workflows [Optional]
Key parameters:
project_slug: Project identifier in formatgh/org/repoorbb/org/repobranch: Git branch to run the pipeline ontag: Git tag to run the pipeline on (mutually exclusive with branch)parameters: Pipeline parameter key-value pairs
Pitfalls:
project_slugformat is{vcs}/{org}/{repo}(e.g.,gh/myorg/myrepo)branchandtagare mutually exclusive; providing both causes an error- Pipeline parameters must match those defined in
.circleci/config.yml - Triggering returns a pipeline ID; workflows start asynchronously
2. Monitor Pipelines and Workflows
When to use: User wants to check the status of pipelines or workflows
Tool sequence:
CIRCLECI_LIST_PIPELINES_FOR_PROJECT- List recent pipelines for a project [Required]CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID- List workflows within a pipeline [Required]CIRCLECI_GET_PIPELINE_CONFIG- View the pipeline configuration used [Optional]
Key parameters:
project_slug: Project identifier in{vcs}/{org}/{repo}formatpipeline_id: UUID of a specific pipelinebranch: Filter pipelines by branch namepage_token: Pagination cursor for next page of results
Pitfalls:
- Pipeline IDs are UUIDs, not numeric IDs
- Workflows inherit the pipeline ID; a single pipeline can have multiple workflows
- Workflow states include: success, running, not_run, failed, error, failing, on_hold, canceled, unauthorized
page_tokenis returned in responses for pagination; continue until absent
3. Inspect Job Details
When to use: User wants to drill into a specific job's execution details
Tool sequence:
CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID- Find workflow containing the job [Prerequisite]CIRCLECI_GET_JOB_DETAILS- Get detailed job information [Required]
Key parameters:
project_slug: Project identifierjob_number: Numeric job number (not UUID)
Pitfalls:
- Job numbers are integers, not UUIDs (unlike pipeline and workflow IDs)
- Job details include executor type, parallelism, start/stop times, and status
- Job statuses: success, running, not_run, failed, retried, timedout, infrastructure_fail, canceled
4. Retrieve Build Artifacts
When to use: User wants to download or list artifacts produced by a job
Tool sequence:
CIRCLECI_GET_JOB_DETAILS- Confirm job completed successfully [Prerequisite]CIRCLECI_GET_JOB_ARTIFACTS- List all artifacts from the job [Required]
Key parameters:
project_slug: Project identifierjob_number: Numeric job number
Pitfalls:
- Artifacts are only available after job completion
- Each artifact has a
pathandurlfor download - Artifact URLs may require authentication headers to download
- Large artifacts may have download size limits
5. Review Test Results
When to use: User wants to check test outcomes for a specific job
Tool sequence:
CIRCLECI_GET_JOB_DETAILS- Verify job ran tests [Prerequisite]CIRCLECI_GET_TEST_METADATA- Retrieve test results and metadata [Required]
Key parameters:
project_slug: Project identifierjob_number: Numeric job number
Pitfalls:
- Test metadata requires the job to have uploaded test results (JUnit XML format)
- If no test results were uploaded, the response will be empty
- Test metadata includes classname, name, result, message, and run_time fields
- Failed tests include failure messages in the
messagefield
Common Patterns
Project Slug Format
Format: {vcs_type}/{org_name}/{repo_name}
- GitHub: gh/myorg/myrepo
- Bitbucket: bb/myorg/myrepo
Pipeline -> Workflow -> Job Hierarchy
1. Call CIRCLECI_LIST_PIPELINES_FOR_PROJECT to get pipeline IDs
2. Call CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID with pipeline_id
3. Extract job numbers from workflow details
4. Call CIRCLECI_GET_JOB_DETAILS with job_number
Pagination
- Check response for
next_page_tokenfield - Pass token as
page_tokenin next request - Continue until
next_page_tokenis absent or null
Known Pitfalls
ID Formats:
- Pipeline IDs: UUIDs (e.g.,
5034460f-c7c4-4c43-9457-de07e2029e7b) - Workflow IDs: UUIDs
- Job numbers: Integers (e.g.,
123) - Do NOT mix up UUIDs and integers between different endpoints
Project Slugs:
- Must include VCS prefix:
gh/for GitHub,bb/for Bitbucket - Organization and repo names are case-sensitive
- Incorrect slug format causes 404 errors
Rate Limits:
- CircleCI API has per-endpoint rate limits
- Implement exponential backoff on 429 responses
- Avoid rapid polling; use reasonable intervals (5-10 seconds)
Quick Reference
| Task | Tool Slug | Key Params |
|---|---|---|
| Trigger pipeline | CIRCLECI_TRIGGER_PIPELINE | project_slug, branch, parameters |
| List pipelines | CIRCLECI_LIST_PIPELINES_FOR_PROJECT | project_slug, branch |
| List workflows | CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID | pipeline_id |
| Get pipeline config | CIRCLECI_GET_PIPELINE_CONFIG | pipeline_id |
| Get job details | CIRCLECI_GET_JOB_DETAILS | project_slug, job_number |
| Get job artifacts | CIRCLECI_GET_JOB_ARTIFACTS | project_slug, job_number |
| Get test metadata | CIRCLECI_GET_TEST_METADATA | project_slug, job_number |
Powered by Composio
More from this repository10
A Claude Code plugin that analyzes meeting notes and transcripts to extract key insights, action items, and decisions using Composio app integrations.
A Claude Code plugin from the Awesome Claude Skills collection that downloads videos from YouTube and other platforms for offline viewing, editing, or archival, with support for various formats and quality options.
A Claude Code plugin that assists in writing high-quality content by conducting research, adding citations, improving hooks, and providing section-by-section feedback.
A Claude Code plugin that automatically organizes and categorizes files in your workspace using Composio integrations, helping maintain a clean project structure.
A Claude Code plugin providing tools for creating elaborate, multi-component HTML artifacts using React, Tailwind CSS, and shadcn/ui in claude.ai.
A Claude Code skill that randomly selects winners from participant lists, spreadsheets, or Google Sheets for giveaways and contests using cryptographically secure randomness.
A Claude Code plugin that automates Zoho CRM workflows including lead management, contact updates, deal tracking, account operations, and custom module interactions through Composio integration.
A Claude Code plugin that enforces brand consistency by checking code and content against your brand guidelines using Composio integrations.
A pre-built workflow skill for automating Help Scout via Composio, enabling Claude to manage conversations, customers, mailboxes, and tags through structured tool sequences and parameter guidance.
A Claude Code plugin that automatically creates user-facing changelogs from git commits by analyzing commit history and transforming technical commits into customer-friendly release notes.