-
Notifications
You must be signed in to change notification settings - Fork 46
Description
Is there an existing issue that is already proposing this?
- I have searched the existing issues
Is your feature request related to a problem with the MCP CircleCI integration?
no
Describe the solution you'd like
Add a new tool called get_all_step_outputs (or get_job_step_outputs) that:
- Accepts the same input options as existing tools (projectSlug + branch, projectURL, or workspace detection)
- Retrieves all step outputs from the latest pipeline (or a specific pipeline/job)
- Returns both successful and failed step outputs
- Optionally supports filtering by job name or step name
example usage:
`// Get all step outputs from latest pipeline
{
"params": {
"projectSlug": "gh/organization/project",
"branch": "main"
}
}
// Optional: Filter by specific job
{
"params": {
"projectSlug": "gh/organization/project",
"branch": "main",
"jobName": "build_apk_for_testing"
}
}`
expected response:
{ "pipeline_number": 123, "workflows": [ { "workflow_name": "build-and-test", "jobs": [ { "job_name": "build_apk_for_testing", "status": "success", "steps": [ { "name": "Checkout code", "status": "success", "output": "..." }, { "name": "Build APK", "status": "success", "output": "..." } ] } ] } ] }
API Endpoints to Use
The CircleCI API v2 provides these endpoints:
GET /pipeline/{pipeline-id}/workflow - Get workflows
GET /workflow/{workflow-id}/job - Get jobs in workflow
GET /project/{project-slug}/{job-number} - Get job details with steps
Implementation and compatibility considerations
corrently nothing
What is the motivation / use case for this feature?
i have an issue retrieving the details of the entire pipeline output.
Those details are important for the agent, as it's the context of my pipeline building process