com.mcparmory/circleci
OCI · GHCR.IO/MCPARMORY/CIRCLECI:1.0.4 · 2 COMPONENTS · SCANNED SEP 20
Manage CI/CD pipelines, workflows, and job metrics across projects
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 14706 tokens (~136/item across 108 items; 108 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 16 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 108 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/circleci MCP server?
com.mcparmory/circleci runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/circleci:1.0.4. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/circleci:1.0.4
claude mcp add com-mcparmory-circleci -- docker run --rm -i ghcr.io/mcparmory/circleci:1.0.4
{
"mcpServers": {
"com-mcparmory-circleci": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/circleci:1.0.4"
]
}
}
} {
"servers": {
"com-mcparmory-circleci": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/circleci:1.0.4"
]
}
}
} codex mcp add com-mcparmory-circleci -- docker run --rm -i ghcr.io/mcparmory/circleci:1.0.4
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-circleci": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/circleci:1.0.4"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-circleci:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/circleci:1.0.4"] {
"McpServers": {
"com-mcparmory-circleci": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/circleci:1.0.4"
]
}
}
} {
"mcpServers": {
"com-mcparmory-circleci": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/circleci:1.0.4"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −2
- Stability: pass → 0.83 functional
- 12 Sept 26 0
- Stability: 0.97 → pass security
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/circleci:1.0.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_pipeline_definition Get Pipeline Definition ~90
Retrieves detailed configuration metadata for a specific pipeline definition within a project. Supported for pipeline definitions using GitHub App, GitHub OAuth, Bitbucket DC, Bitbucket OAuth, or GitLab as the config source provider.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_definition_id | string | yes | The unique opaque identifier of the pipeline definition to retrieve. |
| project_id | string | yes | The unique opaque identifier of the project containing the pipeline definition. |
No output schema declared.
No examples provided.
get_pipeline_values Get Pipeline Values ~71
Retrieves a map of built-in pipeline values (such as pipeline number, trigger parameters, and VCS metadata) for a specific pipeline. Useful for inspecting runtime context associated with a pipeline execution.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline-id | string | yes | The unique identifier of the pipeline whose values you want to retrieve, in UUID format. |
No output schema declared.
No examples provided.
get_policy_bundle Get Policy Bundle ~85
Retrieves the complete policy bundle associated with a specific context for a given owner. Returns all policies grouped within that bundle for review or enforcement purposes.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | The context scope under which the policy bundle is organized, used to namespace or categorize policies for the specified owner. |
| ownerID | string | yes | The unique identifier of the owner whose policy bundle is being retrieved. |
No output schema declared.
No examples provided.
get_project Get Project ~129
Retrieves detailed information about a specific CircleCI project using its unique project slug. Supports projects hosted on GitHub, GitLab, and Bitbucket, including those using the GitHub App integration.
| Name | Type | Req | Description |
|---|---|---|---|
| project-slug | string | yes | Unique identifier for the project in the format `vcs-slug/org-name/repo-name`, where slashes may be URL-escaped. For GitLab or GitHub App projects, use `circleci` as the VCS slug, the organization ID… |
No output schema declared.
No examples provided.
get_project_oidc_claims Get Project OIDC Custom Claims ~83
Retrieves the custom OIDC identity token claims configured at the project level. Use this to inspect which additional claims are included in tokens issued for a specific project.
| Name | Type | Req | Description |
|---|---|---|---|
| orgID | string | yes | The unique identifier of the organization that owns the project. |
| projectID | string | yes | The unique identifier of the project whose custom OIDC claims are being retrieved. |
No output schema declared.
No examples provided.
get_project_settings Get Project Settings ~121
Retrieves the advanced settings for a specified CircleCI project, returning each setting with a boolean indicating whether it is enabled or disabled.
| Name | Type | Req | Description |
|---|---|---|---|
| organization | string | yes | The organization segment of the project slug, which may be an organization name or a unique organization ID depending on the account type. |
| project | string | yes | The project segment of the project slug, which may be a project name or a unique project ID depending on the account type. |
| provider | string | yes | The version control or CI provider portion of the project slug, identifying which platform hosts the project. |
No output schema declared.
No examples provided.
get_project_workflow_summary Get Project Workflow Summary ~233
Retrieves aggregated summary metrics and trends for a project across its workflows and branches, covering up to 90 days of workflow run history. Note: Insights data is not suitable for precise credit reporting; use the CircleCI Plan Overview page for billing accuracy.
| Name | Type | Req | Description |
|---|---|---|---|
| branches | object | – | One or more VCS branch names to filter branch-level workflow metrics. Multiple branches can be specified by repeating the query parameter. |
| project-slug | string | yes | The project slug identifying the target project, formed as `vcs-slug/org-name/repo-name`. For GitLab or GitHub App projects, use `circleci` as the vcs-slug, the organization ID as org-name, and the p… |
| reporting-window | string | – | The time window over which summary metrics are calculated. Trends are only supported for windows up to 30 days; defaults to last-90-days if omitted. |
| workflow-names | object | – | One or more workflow names to filter workflow-level metrics. Multiple workflow names can be specified by repeating the query parameter. |
No output schema declared.
No examples provided.
get_schedule Get Schedule ~57
Retrieves the details of a specific pipeline schedule by its unique ID. Only available for schedules associated with GitHub OAuth or Bitbucket Cloud pipeline definitions.
| Name | Type | Req | Description |
|---|---|---|---|
| schedule-id | string | yes | The unique identifier of the schedule to retrieve, in UUID format. |
No output schema declared.
No examples provided.
get_trigger Get Trigger ~78
Retrieves detailed configuration and metadata for a specific project trigger. Currently supported for triggers with GitHub OAuth, GitHub App, Bitbucket Data Center, or webhook event sources.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The unique opaque identifier of the project that owns the trigger. |
| trigger_id | string | yes | The unique opaque identifier of the trigger to retrieve. |
No output schema declared.
No examples provided.
get_usage_export_job Get Usage Export Job ~77
Retrieves the status and details of a specific usage export job for an organization, including download information once the export is complete.
| Name | Type | Req | Description |
|---|---|---|---|
| org_id | string | yes | The unique opaque identifier of the organization whose usage export job is being retrieved. |
| usage_export_job_id | string | yes | The unique UUID identifier of the usage export job to retrieve. |
No output schema declared.
No examples provided.
get_user Get User ~53
Retrieves profile and account information for a specific user. Use this to look up user details by their unique identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the user whose information should be retrieved, provided as a UUID. |
No output schema declared.
No examples provided.
get_webhook Get Webhook ~62
Retrieves the configuration and details of a specific outbound webhook by its unique identifier. Use this to inspect webhook settings such as target URL, events, and status.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook-id | string | yes | The unique identifier of the outbound webhook to retrieve, provided as a UUID. |
No output schema declared.
No examples provided.
get_workflow Get Workflow ~55
Retrieves summary fields for a specific workflow by its unique identifier. Useful for checking workflow metadata such as name, status, and configuration details.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the workflow to retrieve, in UUID format. |
No output schema declared.
No examples provided.
get_workflow_summary Get Workflow Summary ~201
Retrieves aggregated metrics and trends for a specific workflow within a project, such as duration, success rate, and run frequency. Results can be scoped to a single branch or aggregated across all branches.
| Name | Type | Req | Description |
|---|---|---|---|
| all-branches | boolean | – | When set to true, aggregates metrics across all branches instead of a single branch. Use either this parameter or the branch parameter, not both. |
| branch | string | – | The name of the VCS branch to scope metrics to. If omitted and all-branches is not set, results default to the repository's default branch. |
| project-slug | string | yes | Unique identifier for the project, formatted as vcs-slug/org-name/repo-name. For GitLab or GitHub App projects, use 'circleci' as the vcs-slug, the organization ID as org-name, and the project ID as… |
| workflow-name | string | yes | The exact name of the workflow for which to retrieve summary metrics. |
No output schema declared.
No examples provided.
get_workflow_test_metrics Get Workflow Test Metrics ~227
Retrieves test metrics for a specific workflow within a project, calculated from the 10 most recent workflow runs. Results can be scoped to a specific branch or aggregated across all branches.
| Name | Type | Req | Description |
|---|---|---|---|
| all-branches | boolean | – | When set to true, aggregates test metrics across all branches rather than a single branch. Mutually exclusive with the branch parameter; use one or the other, not both. |
| branch | string | – | Scopes results to a specific VCS branch name. Defaults to the repository's default branch if omitted. Mutually exclusive with the all-branches parameter. |
| project-slug | string | yes | Unique identifier for the project in the format `vcs-slug/org-name/repo-name`. For GitLab or GitHub App projects, use `circleci` as the vcs-slug, the organization ID (from Organization Settings) as o… |
| workflow-name | string | yes | The exact name of the workflow for which test metrics should be retrieved. |
No output schema declared.
No examples provided.
list_checkout_keys List Checkout Keys ~155
Retrieves all checkout keys associated with a specified project, returning their fingerprints and metadata. Useful for auditing or managing SSH keys used during CI/CD checkout steps.
| Name | Type | Req | Description |
|---|---|---|---|
| digest | string | – | The hashing algorithm used to format the returned key fingerprints; accepted values are `md5` or `sha256`, defaulting to `md5` if omitted. |
| project-slug | string | yes | The project slug uniquely identifying the project, formatted as `vcs-slug/org-name/repo-name`. For GitLab or GitHub App projects, use `circleci` as the vcs-slug, the organization ID in place of org-n… |
No output schema declared.
No examples provided.
list_collaborations List Collaborations ~51
Retrieves all organizations where the current user is a member or collaborator, spanning multiple VCS providers (e.g., GitHub, BitBucket), parent organizations of accessible repositories, and the user's own account organization.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_component_versions List Component Versions ~87
Retrieves all available versions for a specified component. Optionally filter results by environment to see versions relevant to a particular deployment context.
| Name | Type | Req | Description |
|---|---|---|---|
| component_id | string | yes | The unique identifier of the component whose versions you want to retrieve. |
| environment-id | string | – | The unique identifier of an environment to filter component versions by, returning only versions relevant to that environment. Must be a valid UUID. |
No output schema declared.
No examples provided.
list_components List Components ~113
Retrieves a paginated list of deployed components belonging to a specified organization. Optionally filter results by project to narrow the scope of returned components.
| Name | Type | Req | Description |
|---|---|---|---|
| org-id | string | yes | The unique identifier of the organization whose components will be listed. |
| page-size | integer | yes | The maximum number of components to return in a single page of results. Use in combination with pagination tokens to iterate through all components. |
| project-id | string | – | The unique identifier of a project used to filter components to only those belonging to that project. |
No output schema declared.
No examples provided.
list_context_environment_variables List Context Environment Variables ~54
Retrieves a list of environment variables defined within a specified context, returning metadata such as names but excluding their values for security.
| Name | Type | Req | Description |
|---|---|---|---|
| context_id | string | yes | The unique identifier of the context whose environment variables should be listed. |
No output schema declared.
No examples provided.
list_context_restrictions List Context Restrictions ~60
Retrieves all project and expression restrictions associated with a specific context. Returns the complete list of restrictions currently applied to the given context.
| Name | Type | Req | Description |
|---|---|---|---|
| context_id | string | yes | The unique identifier of the context whose restrictions should be retrieved, provided as a UUID. |
No output schema declared.
No examples provided.
list_contexts List Contexts ~157
Retrieves all contexts belonging to a specified organization or owner, enabling management of shared environment variables and secrets across projects.
| Name | Type | Req | Description |
|---|---|---|---|
| owner-id | string | – | The unique UUID of the organization that owns the contexts. Use this or owner-slug to identify the organization — find both in CircleCI web app under Organization Settings > Overview. |
| owner-slug | string | – | The slug identifier for the organization that owns the contexts. Use this or owner-id to identify the organization — find both in CircleCI web app under Organization Settings > Overview. Not supporte… |
| owner-type | string | – | Specifies whether the owner is an organization or an individual account. Defaults to 'organization'; use 'account' when working with CircleCI server. |
No output schema declared.
No examples provided.
list_decision_logs List Decision Logs ~250
Retrieves a paginated list of policy decision audit logs for the specified owner and context. Results can be filtered by status, date range, branch, project, or build number.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Filters results to only include decisions made after this timestamp. Must be a valid ISO 8601 date-time string. |
| before | string | – | Filters results to only include decisions made before this timestamp. Must be a valid ISO 8601 date-time string. |
| branch | string | – | Filters results to only include decisions made on the specified branch name. |
| build_number | string | – | Filters results to only include decisions associated with the specified build number. |
| context | string | yes | The policy context scope under which decisions were evaluated and logged. |
| offset | integer | – | The number of records to skip before returning results, enabling pagination through large result sets. |
| ownerID | string | yes | The unique identifier of the owner whose policy decision logs are being retrieved. |
| project_id | string | – | Filters results to only include decisions associated with the specified project identifier. |
| status | string | – | Filters results to only include decisions that match the specified decision status (e.g., approved or rejected). |
No output schema declared.
No examples provided.
list_env_vars List Environment Variables ~130
Retrieves all environment variables for a specified CircleCI project. Values are masked, returning only the last four characters prefixed with four 'x' characters, matching the display behavior on the CircleCI website.
| Name | Type | Req | Description |
|---|---|---|---|
| project-slug | string | yes | Unique identifier for the project, formatted as `vcs-slug/org-name/repo-name`. For GitLab or GitHub App projects, use `circleci` as the vcs-slug, the organization ID (from Organization Settings) as o… |
No output schema declared.
No examples provided.
list_environments List Environments ~90
Retrieves a paginated list of deployment environments belonging to a specified organization. Use this to browse available environments for deployment targeting or configuration management.
| Name | Type | Req | Description |
|---|---|---|---|
| org-id | string | yes | The unique identifier of the organization whose environments you want to list, provided as a UUID. |
| page-size | integer | yes | The maximum number of environments to return per page. Use this alongside pagination controls to iterate through large result sets. |
No output schema declared.
No examples provided.
list_flaky_tests List Flaky Tests ~125
Retrieves all flaky tests for a given project, where a flaky test is defined as one that both passed and failed within the same commit. Results are branch-agnostic.
| Name | Type | Req | Description |
|---|---|---|---|
| project-slug | string | yes | Unique identifier for the project, formatted as `vcs-slug/org-name/repo-name`. For GitLab or GitHub App projects, use `circleci` as the vcs-slug, the organization ID (from Organization Settings) as o… |
No output schema declared.
No examples provided.
list_job_artifacts List Job Artifacts ~132
Retrieves all artifacts produced by a specific job in a CircleCI project. Useful for accessing build outputs such as test reports, binaries, or logs.
| Name | Type | Req | Description |
|---|---|---|---|
| job-number | – | yes | The unique number identifying the job within the project whose artifacts you want to retrieve. |
| project-slug | string | yes | Project slug uniquely identifying the project in the format `vcs-slug/org-name/repo-name`. For GitLab or GitHub App projects, use `circleci` as the vcs-slug, the organization ID as org-name, and the… |
No output schema declared.
No examples provided.
list_job_tests List Job Tests ~133
Retrieves test metadata for a specific job within a project, including results and timing information. Returns no results if test data exceeds 250MB for the job.
| Name | Type | Req | Description |
|---|---|---|---|
| job-number | – | yes | The unique numeric identifier of the job whose test metadata you want to retrieve. |
| project-slug | string | yes | Project slug identifying the target project in the format `vcs-slug/org-name/repo-name`, where URL-escaping of `/` is supported. For GitLab or GitHub App projects, use `circleci` as the vcs-slug, the… |
No output schema declared.
No examples provided.
list_job_timeseries List Job Timeseries ~289
Retrieve timeseries performance data for all jobs within a specified workflow, supporting hourly or daily granularity. Hourly data is retained for 48 hours and daily data for 90 days.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | The name of the VCS branch to scope results to. Defaults to the repository's default branch if omitted. |
| end-date | string | – | The exclusive end of the time range filter, in ISO 8601 date-time format. Must be no more than 90 days after the start-date. |
| granularity | string | – | The time resolution for the returned timeseries data, either per hour or per day. Hourly data is only available for the past 48 hours; daily data is available for up to 90 days. |
| project-slug | string | yes | Unique identifier for the project in the format `vcs-slug/org-name/repo-name`, where slashes may be URL-escaped. For GitLab or GitHub App projects, use `circleci` as the vcs-slug, the organization ID… |
| start-date | string | – | The inclusive start of the time range filter, in ISO 8601 date-time format. Must be provided if an end-date is specified. |
| workflow-name | string | yes | The exact name of the workflow for which to retrieve job timeseries data. |
No output schema declared.
No examples provided.
list_my_pipelines List My Pipelines ~116
Retrieves all pipelines for a specified project that were triggered by the authenticated user. Returns results as a sequence ordered by trigger time.
| Name | Type | Req | Description |
|---|---|---|---|
| project-slug | string | yes | Unique identifier for the project, formatted as `vcs-slug/org-name/repo-name`. For GitLab or GitHub App projects, use `circleci` as the vcs-slug, the organization ID (from Organization Settings) as o… |
No output schema declared.
No examples provided.
list_org_oidc_custom_claims List Organization OIDC Custom Claims ~65
Retrieves the org-level custom claims configured for OIDC identity tokens. Use this to inspect which additional claims are included in tokens issued for the specified organization.
| Name | Type | Req | Description |
|---|---|---|---|
| orgID | string | yes | The unique identifier of the organization whose OIDC custom claims should be retrieved. |
No output schema declared.
No examples provided.
list_organization_groups List Organization Groups ~80
Retrieves all groups belonging to a specified organization. Supports pagination to control the number of results returned per page.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | The maximum number of group results to return per page. Use this to control pagination when an organization has many groups. |
| org_id | string | yes | The unique identifier of the organization whose groups you want to retrieve. |
No output schema declared.
No examples provided.
list_otel_exporters List OTel Exporters ~66
Retrieves all OpenTelemetry (OTLP) exporter configurations associated with the specified organization. This is an experimental feature and may be subject to change.
| Name | Type | Req | Description |
|---|---|---|---|
| org-id | string | yes | The unique identifier of the organization whose OTLP exporter configurations should be retrieved, provided as a UUID. |
No output schema declared.
No examples provided.
list_pipeline_definition_triggers List Pipeline Definition Triggers ~89
Retrieves all triggers configured for a specific pipeline definition within a project. Supported only for pipeline definitions using GitHub OAuth, GitHub App, or Bitbucket Data Center as the config source provider.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_definition_id | string | yes | The unique identifier of the pipeline definition whose triggers you want to list. |
| project_id | string | yes | The unique identifier of the project containing the pipeline definition. |
No output schema declared.
No examples provided.
list_pipeline_definitions List Pipeline Definitions ~54
Retrieves all pipeline definitions associated with a specified project. Pipeline definitions describe the structure and configuration of pipelines available within the project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The unique identifier of the project whose pipeline definitions should be listed. |
No output schema declared.
No examples provided.
list_pipeline_workflows List Pipeline Workflows ~65
Retrieves a paginated list of workflows associated with a specific pipeline. Use this to inspect all workflows belonging to a given pipeline by its unique identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline-id | string | yes | The unique identifier of the pipeline whose workflows you want to retrieve. Must be a valid UUID. |
No output schema declared.
No examples provided.
list_pipelines List Pipelines ~124
Retrieves up to 250 pipelines from the most recently built projects you follow within an organization. Optionally filter by organization or limit results to pipelines triggered by your user.
| Name | Type | Req | Description |
|---|---|---|---|
| mine | boolean | – | When set to true, restricts results to only pipelines triggered by the authenticated user. |
| org-slug | string | – | The organization slug identifying the target organization, formatted as vcs-slug/org-name. For GitLab or GitHub App projects, use 'circleci' as the vcs-slug and supply the organization ID (found in O… |
No output schema declared.
No examples provided.
list_project_branches List Project Branches ~144
Retrieves all branches currently tracked within Insights for a specified project. Returns up to 5,000 branches, optionally scoped to a specific workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| project-slug | string | yes | Unique identifier for the project, formatted as `vcs-slug/org-name/repo-name`. For GitLab or GitHub App projects, use `circleci` as the vcs-slug, the organization ID as org-name, and the project ID a… |
| workflow-name | string | – | Filters the returned branches to only those associated with the specified workflow name. When omitted, branches are scoped to the entire project across all workflows. |
No output schema declared.
No examples provided.
list_project_pipelines List Project Pipelines ~146
Retrieves all pipelines for a specified project, optionally filtered by branch. Useful for monitoring CI/CD activity and pipeline history across a project.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Filters returned pipelines to only those triggered on the specified branch name. When omitted, pipelines from all branches are returned. |
| project-slug | string | yes | Unique identifier for the project in the format `vcs-slug/org-name/repo-name`. For GitLab or GitHub App projects, use `circleci` as the vcs-slug, the organization ID (from Organization Settings) as o… |
No output schema declared.
No examples provided.
list_project_schedules List Project Schedules ~135
Retrieves all schedule triggers associated with GitHub OAuth or Bitbucket Cloud pipeline definitions for a given project. Note: schedules for GitHub App pipelines are not included and must be fetched via the List Pipeline Definition Triggers endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| project-slug | string | yes | Unique identifier for the project in the format `vcs-slug/org-name/repo-name`. For GitLab or GitHub App projects, use `circleci` as the vcs-slug, the organization ID (from Organization Settings) as o… |
No output schema declared.
No examples provided.
list_url_orb_allow_list_entries List URL Orb Allow List Entries ~113
Retrieves all entries in the URL Orb allow-list for the specified organization. Use this to review which URLs are permitted under the org's URL Orb configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| org-slug-or-id | string | yes | The organization identifier, either as a UUID or a slug in the format `vcs-slug/org-name`. For organizations using GitLab or GitHub App, use `circleci` as the VCS slug and provide the organization ID… |
No output schema declared.
No examples provided.
list_webhooks List Webhooks ~92
Retrieves all outbound webhooks associated with a given scope. Currently supports project-level scoping by providing a project ID.
| Name | Type | Req | Description |
|---|---|---|---|
| scope-id | string | yes | The unique identifier of the scope entity to filter webhooks by. Currently only project IDs are supported. |
| scope-type | string | yes | The type of scope used to filter webhooks. Determines how the scope-id is interpreted; currently only 'project' is supported. |
No output schema declared.
No examples provided.
list_workflow_job_metrics List Workflow Job Metrics ~286
Retrieves aggregated summary metrics for all jobs within a specific project workflow, covering up to the last 90 days. Metrics are refreshed daily and are intended for performance analysis, not precise credit or billing reporting.
| Name | Type | Req | Description |
|---|---|---|---|
| all-branches | boolean | – | When set to true, aggregates metrics across all branches. Use either this parameter or the branch parameter, not both. |
| branch | string | – | Filters metrics to a specific VCS branch by name. Defaults to the repository's default branch if neither this nor all-branches is provided. |
| job-name | string | – | Filters results to jobs whose names match the provided string, either as a full job name or a substring. Returns metrics for all jobs in the workflow if omitted. |
| project-slug | string | yes | Unique identifier for the project in the form `vcs-slug/org-name/repo-name`. For GitLab or GitHub App projects, use `circleci` as the vcs-slug, the organization ID (from Organization Settings) as org… |
| reporting-window | string | – | Defines the time window over which summary metrics are calculated. Defaults to the last 90 days if not specified. |
| workflow-name | string | yes | The exact name of the workflow whose job metrics you want to retrieve. |
No output schema declared.
No examples provided.
list_workflow_jobs List Workflow Jobs ~56
Retrieves the ordered sequence of jobs associated with a specific workflow. Use this to inspect all jobs belonging to a workflow and their current states.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the workflow whose jobs you want to retrieve. |
No output schema declared.
No examples provided.
list_workflow_metrics List Workflow Metrics ~193
Retrieves aggregated summary metrics for all workflows in a project, covering up to the last 90 days. Metrics are refreshed daily and are intended for performance insights, not precise credit or billing reporting.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Filters metrics to a specific VCS branch by name. If omitted, metrics are scoped to the project's default branch. |
| project-slug | string | yes | Unique identifier for the project in the format `vcs-slug/org-name/repo-name`. For GitLab or GitHub App projects, use `circleci` as the vcs-slug, the Organization ID (from Organization Settings) as o… |
| reporting-window | string | – | Defines the time window over which summary metrics are calculated. Accepts predefined window values; if omitted, defaults to the last 90 days. |
No output schema declared.
No examples provided.
list_workflow_runs List Workflow Runs ~296
Retrieves recent runs of a specific workflow within a project, covering executions up to 90 days in the past. Note that Insights data is not suitable for precise credit reporting; use the CircleCI UI Plan Overview page for accurate billing information.
| Name | Type | Req | Description |
|---|---|---|---|
| all-branches | boolean | – | When set to true, aggregates data across all branches. Use either this parameter or the branch parameter, but not both simultaneously. |
| branch | string | – | Filters results to a specific VCS branch by name. Defaults to the repository's default branch if omitted; cannot be used together with all-branches. |
| end-date | string | – | Filters results to only include workflow runs that started before this ISO 8601 datetime. Must be no more than 90 days after the start-date. |
| project-slug | string | yes | Unique identifier for the project in the format `vcs-slug/org-name/repo-name`, where slashes may be URL-escaped. For GitLab or GitHub App projects, use `circleci` as the vcs-slug, the Organization ID… |
| start-date | string | – | Filters results to only include workflow runs that started at or after this ISO 8601 datetime. Required when an end-date is specified. |
| workflow-name | string | yes | The exact name of the workflow whose runs you want to retrieve, as defined in the project's pipeline configuration. |
No output schema declared.
No examples provided.
rerun_workflow Rerun Workflow ~213
Reruns an existing workflow by its ID, with options to rerun from the first failed job, target specific jobs, or apply sparse tree optimization for complex workflow graphs.
| Name | Type | Req | Description |
|---|---|---|---|
| enable_ssh | boolean | – | When true, enables SSH access for the triggering user on the newly rerun job. Requires the jobs parameter to be specified and is mutually exclusive with from_failed. |
| from_failed | boolean | – | When true, reruns the workflow starting from the first failed job rather than the beginning. Mutually exclusive with the jobs and sparse_tree parameters. |
| id | string | yes | The unique identifier of the workflow to rerun. |
| jobs | array | – | A list of specific job IDs (UUIDs) to rerun within the workflow. Order is not significant. Mutually exclusive with from_failed. |
| sparse_tree | boolean | – | When true, applies sparse tree optimization logic during the rerun, improving performance for workflows containing disconnected subgraphs. Requires the jobs parameter and is mutually exclusive with f… |
No output schema declared.
No examples provided.
rollback_project Rollback Project ~248
Rolls back a specific component in a project to a target version by triggering a rollback pipeline. Use this to recover from a bad deployment by reverting a component from its current version to a previously stable version.
| Name | Type | Req | Description |
|---|---|---|---|
| component_name | string | yes | The name of the component within the project to be rolled back. |
| current_version | string | yes | The version of the component currently deployed, which will be replaced by the rollback. |
| environment_name | string | yes | The name of the environment in which the rollback will be executed (e.g., production, staging). |
| namespace | string | – | The Kubernetes or deployment namespace where the component resides. Defaults to the project's default namespace if not specified. |
| parameters | object | – | A key-value map of additional parameters to pass to the rollback pipeline, allowing customization of pipeline behavior beyond standard inputs. |
| project_id | string | yes | The unique opaque identifier of the project in which the rollback will be performed. |
| reason | string | – | A human-readable explanation for why the rollback is being performed, useful for audit trails and incident tracking. |
| target_version | string | yes | The version to roll back to, which should be a previously stable and deployed version of the component. |
No output schema declared.
No examples provided.
set_context_environment_variable Set Context Environment Variable ~105
Creates or updates a named environment variable within a specified context. Returns metadata about the variable after the operation, excluding its value.
| Name | Type | Req | Description |
|---|---|---|---|
| context_id | string | yes | The unique identifier of the context in which to create or update the environment variable. |
| env_var_name | string | yes | The name of the environment variable to create or update within the context. |
| value | string | – | The value to assign to the environment variable; treated as a secret and not returned in responses. |
No output schema declared.
No examples provided.
trigger_pipeline Trigger Pipeline ~274
Triggers a new pipeline run on a specified project using a branch, tag, or custom parameters. Note: this endpoint does not support GitLab or GitHub App projects — use the Trigger Pipeline Run API for those.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | The branch to run the pipeline against, using the HEAD commit of that branch. Mutually exclusive with `tag`; only one may be provided. To target a pull request, use `pull/<number>/head` for the PR re… |
| parameters | object | – | A key-value map of pipeline parameter names to their values, used to customize the pipeline run. Limited to 100 entries, with keys up to 128 characters and values up to 512 characters each. |
| project-slug | string | yes | Unique identifier for the project in the format `vcs-slug/org-name/repo-name`, where forward slashes may be URL-encoded. For GitLab or GitHub App projects, use `circleci` as the vcs-slug with the org… |
| tag | string | – | A Git tag whose pointed-to commit will be used for the pipeline run. Mutually exclusive with `branch`; only one may be provided. |
No output schema declared.
No examples provided.
What is the com.mcparmory/circleci MCP server?
com.mcparmory/circleci is an MCP server listed in the public MCP registry as com.mcparmory/circleci. Manage CI/CD pipelines, workflows, and job metrics across projects. This page covers its container image (ghcr.io/mcparmory/circleci:1.0.4).
Is the com.mcparmory/circleci MCP server safe to use?
com.mcparmory/circleci scores 50 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/circleci MCP server expose?
com.mcparmory/circleci exposes 108 tools: get_project_workflow_summary, list_job_timeseries, get_org_summary, list_project_branches, list_flaky_tests, and 103 more. Their descriptions and schemas cost roughly 14,706 tokens of context every time the server is loaded.
Is the com.mcparmory/circleci MCP server still maintained?
com.mcparmory/circleci is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.