circleci-automationlisted

# CircleCI Automation via Rube MCP Automate CircleCI CI/CD operations through Composio's CircleCI toolkit via Rube MCP. ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active CircleCI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `circleci` - Always call `RUBE_SEARCH_TOOLS` first 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. 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `circleci` 3. If connection is not ACTIVE, follow the returned auth link to complete CircleCI authentication 4. 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**: 1. `CIRCLECI_TRIGGER_PIPELINE` - Trigger a new pipeline on a project [Required] 2. `CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID` - Monitor resulting workflows [Optional] **Key parameters**: - `project_slug`: Project identifier in format `gh/org/repo` or `bb/org/repo` - `branch`: Git branch to run the pipeline on - `tag`: Git tag to run the pipeline on (mutually exclusive with branch) - `parameters`: Pipeline parameter key-value pairs **Pitfalls**: - `project_slug` format is `{vcs}/{org}/{repo}` (e.g., `gh/myorg/myrepo`) - `branch` and `tag` are mutually