com.mcparmory/circleci
PYPI · MCPARMORY-CIRCLECI · 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 Security37
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
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: the license (MIT License) isn't a recognized OSI-approved license. 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 Management87
- Stability observed for 26 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 current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/circleci MCP server?
com.mcparmory/circleci runs locally as a PyPI package, launched with uvx mcparmory-circleci. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-circleci
claude mcp add com-mcparmory-circleci -- uvx mcparmory-circleci
{
"mcpServers": {
"com-mcparmory-circleci": {
"command": "uvx",
"args": [
"mcparmory-circleci"
]
}
}
} {
"servers": {
"com-mcparmory-circleci": {
"command": "uvx",
"args": [
"mcparmory-circleci"
]
}
}
} codex mcp add com-mcparmory-circleci -- uvx mcparmory-circleci
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-circleci": {
"type": "local",
"command": [
"uvx",
"mcparmory-circleci"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-circleci --command uvx --arg mcparmory-circleci
mcp_servers:
com-mcparmory-circleci:
command: "uvx"
args: ["mcparmory-circleci"] {
"McpServers": {
"com-mcparmory-circleci": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-circleci"
]
}
}
} assistant mcp add com-mcparmory-circleci -t stdio -c uvx -a mcparmory-circleci
{
"mcpServers": {
"com-mcparmory-circleci": {
"command": "uvx",
"args": [
"mcparmory-circleci"
]
}
}
} 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.
- 19 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.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 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.
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +13
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.83 functional
- 11 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 10 Sept 26 +16
- Malware scan: unverified → pass ▲ security
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 pypi/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 | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
add_context_restriction Add Context Restriction ~156
Adds an access restriction to a context, limiting its use to specific projects, groups, or expression-based rules. Use this to control which projects or conditions are permitted to access the context.
| Name | Type | Req | Description |
|---|---|---|---|
| context_id | string | yes | The unique identifier of the context to which the restriction will be added. |
| restriction_type | string | – | The category of restriction to apply: 'project' limits access to a specific project, 'expression' applies a rule-based condition, and 'group' restricts access to a specific group. |
| restriction_value | string | – | The value that defines the restriction rule, interpreted based on the restriction type: a project UUID for 'project' restrictions, or an expression rule string for 'expression' restrictions. |
No output schema declared.
No examples provided.
approve_workflow_job Approve Workflow Job ~76
Approves a pending approval job within a specified workflow, allowing the workflow to continue past the approval gate.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_request_id | string | yes | The unique identifier of the pending approval job to approve, in UUID format. |
| id | string | yes | The unique identifier of the workflow containing the pending approval job, in UUID format. |
No output schema declared.
No examples provided.
cancel_job Cancel Job ~56
Cancels an active job identified by its unique job ID. Use this to stop a job that is pending or in progress before it completes.
| Name | Type | Req | Description |
|---|---|---|---|
| job-id | string | yes | The unique identifier of the job to cancel, in UUID format. |
No output schema declared.
No examples provided.
cancel_job_by_number Cancel Job by Number ~121
Cancels a running job in a specified project using its job number. Useful for stopping unwanted or erroneous builds mid-execution.
| Name | Type | Req | Description |
|---|---|---|---|
| job-number | – | yes | The unique numeric identifier of the job to cancel within the project. |
| project-slug | string | yes | Project slug identifying the target 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 projec… |
No output schema declared.
No examples provided.
cancel_workflow Cancel Workflow ~62
Cancels a currently running workflow, halting any further execution. Use this to stop a workflow that is in progress before it completes naturally.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the workflow to cancel. Must correspond to an existing, currently running workflow. |
No output schema declared.
No examples provided.
continue_pipeline Continue Pipeline ~140
Resumes a pipeline from the setup phase using a continuation key, allowing dynamic configuration and parameter injection. Refer to the Pipeline values and parameters documentation for guidance on using pipeline parameters with dynamic configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| configuration | string | – | The full pipeline configuration string to apply when continuing the pipeline, used to supply dynamic configuration at runtime. |
| continuation-key | string | – | The unique continuation key that identifies the paused pipeline to resume, obtained from the pipeline setup phase. |
| parameters | object | – | A key-value map of pipeline parameter names to their values, subject to limits of 100 max entries, 128-character maximum key length, and 512-character maximum value length. |
No output schema declared.
No examples provided.
create_checkout_key Create Checkout Key ~156
Creates a new checkout key (deploy key or user key) for a specified project. Only available for GitHub and Bitbucket projects using a user API token; requires GitHub account authorization before creating user keys.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 with the organization ID and project ID in pl… |
| type | string | – | The type of checkout key to create: 'deploy-key' grants read-only repository access for deployments, while 'user-key' grants access tied to a specific GitHub user account. |
No output schema declared.
No examples provided.
create_context Create Context ~79
Creates a new named context within a specified organization, allowing you to group and manage related environment variables or secrets.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | The human-readable name to assign to the new context, used to identify it within the organization. |
| owner | – | – | The owner of the context, typically representing the organization or account under which the context will be created. |
No output schema declared.
No examples provided.
create_env_var Create Environment Variable ~183
Creates a new environment variable for a specified CircleCI project, making it available to pipelines and jobs running within that project.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | The name of the environment variable to create, which must be unique within the project and will be used to reference the variable in pipeline configurations. |
| project-slug | string | yes | The project slug uniquely identifying the target 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 Orga… |
| value | string | – | The value to assign to the environment variable; once stored, this value will be masked and not returned in plaintext by the API. |
No output schema declared.
No examples provided.
create_group Create Group ~99
Creates a new group within a standalone organization, allowing members and resources to be organized under a named group. Only supported for standalone organizations.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | An optional human-readable description providing additional context or purpose for the group. |
| name | string | yes | The display name for the new group, used to identify it within the organization. |
| org_id | string | yes | The unique opaque identifier of the organization under which the group will be created. |
No output schema declared.
No examples provided.
create_organization Create Organization ~90
Creates a new organization, either by validating access and syncing data for a VCS provider (GitHub or Bitbucket), or by provisioning a standalone CircleCI organization.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | The display name for the organization being created. |
| vcs_type | string | – | The version control system associated with the organization, or 'circleci' for a standalone organization not tied to a VCS provider. |
No output schema declared.
No examples provided.
create_otlp_exporter Create OTLP Exporter ~194
Creates a new OTLP exporter configuration for a specified organization, defining how telemetry spans are exported to an external observability backend. This is an experimental feature supporting both gRPC and HTTP transport protocols.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | The destination OTLP collector endpoint, specified as hostname and port only — omit any scheme prefix such as https:// or grpc://. |
| headers | object | – | A key-value map of additional HTTP or gRPC headers to include with every export request, useful for authentication tokens or routing metadata. |
| insecure | boolean | – | When set to true, the exporter connects to the endpoint without TLS encryption; defaults to false for secure connections. |
| org_id | string | yes | The unique identifier of the organization for which the OTLP exporter will be created. |
| protocol | string | yes | The transport protocol used when exporting telemetry data; choose grpc for gRPC transport or http for HTTP/protobuf transport. |
No output schema declared.
No examples provided.
create_pipeline_definition Create Pipeline Definition ~195
Creates a new pipeline definition for a specified project, allowing you to define the configuration source and metadata. Currently only supported for projects using the GitHub App integration provider.
| Name | Type | Req | Description |
|---|---|---|---|
| config_source | – | – | The configuration source object that specifies where and how the pipeline configuration is sourced, including the provider and repository details. |
| description | string | – | An optional description providing additional context or details about the purpose of this pipeline definition. |
| external_id | string | – | The external identifier for the repository as defined by the version control provider, used to link the pipeline definition to the correct repository. |
| name | string | – | A human-readable name for the pipeline definition to distinguish it within the project. |
| project_id | string | yes | The unique opaque identifier of the project under which the pipeline definition will be created. |
| provider | string | – | The version control integration provider for the pipeline definition's configuration source. Currently only 'github_app' is supported. |
No output schema declared.
No examples provided.
create_pipeline_trigger Create Pipeline Trigger ~421
Creates a trigger for a specified pipeline definition, enabling automated pipeline runs in response to events. Currently supported only for pipeline definitions using GitHub OAuth or GitHub App as the config source provider.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_ref | string | – | The Git ref used to check out source code for pipeline runs created by this trigger. Required when the provider is `webhook`; for `github_app`, only provide this if the event source repository differ… |
| config_ref | string | – | The Git ref used to fetch the pipeline configuration for runs created by this trigger. Required when the provider is `webhook`; for `github_app`, only provide this if the event source repository diff… |
| disabled | boolean | – | When set to `true`, the trigger is created in a disabled state and will not fire until explicitly enabled. Not supported for pipeline definitions using `github_oauth` as the config source provider. |
| event_name | string | – | The name of the event that activates this trigger. Should only be set when the provider is `webhook`. |
| event_preset | string | – | Specifies which category of events will activate this trigger using a named preset. Only applicable when `event_source.provider` is `github_app`; choose from the supported preset values to control wh… |
| external_id | string | – | The repository identifier as defined by the version control provider, used to associate the trigger with a specific repository. |
| pipeline_definition_id | string | yes | The unique opaque identifier of the pipeline definition for which the trigger will be created. |
| project_id | string | yes | The unique opaque identifier of the project in which the pipeline definition resides. |
| provider | string | – | The version control or integration provider for the trigger's event source. Accepted values are `github_app`, `github_oauth`, and `webhook`. |
| sender | string | – | Identifies the entity sending the webhook event; only applicable when the provider is `webhook`. |
No output schema declared.
No examples provided.
create_project Create Project ~139
Creates a new project within the specified organization. Works across all organization types including GitHub, GitLab, and CircleCI-managed organizations.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | The display name for the new project. Should be unique within the organization and clearly identify the project. |
| org-slug-or-id | string | yes | The unique identifier for the organization, either as a UUID or a VCS-based slug in the format `vcs-slug/org-name`. For organizations using GitLab or GitHub App integrations, use `circleci` as the VC… |
No output schema declared.
No examples provided.
create_schedule Create Schedule ~263
Creates a recurring pipeline schedule for a project and returns the created schedule. Available only for Bitbucket and GitHub OAuth organizations; for GitHub App or CircleCI project types, use the Create Trigger endpoint instead.
| Name | Type | Req | Description |
|---|---|---|---|
| attribution-actor | string | – | Determines which actor's permissions are used when the scheduled pipeline runs — `current` uses the token owner's permissions, while `system` uses neutral system-level permissions. |
| description | string | – | An optional human-readable description providing additional context about the schedule's purpose or behavior. |
| name | string | – | A human-readable name for the schedule used to identify it within the project. |
| parameters | object | – | Key-value pairs of pipeline parameters passed to each triggered pipeline run; must include at least a `branch` or `tag` key to specify the target ref. |
| project-slug | string | yes | The project identifier in the format `vcs-slug/org-name/repo-name`, where forward slashes may be URL-escaped. For GitLab or GitHub App projects, use `circleci` as the vcs-slug with the organization I… |
| timetable | – | – | The timetable definition specifying when the schedule should trigger, including frequency, days, and time settings. |
No output schema declared.
No examples provided.
create_url_orb_allow_list_entry Create URL Orb Allow List Entry ~165
Adds a new URL prefix entry to an organization's URL Orb allow-list, permitting orb references that begin with the specified URL prefix to be used in pipelines.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | A human-readable label for this allow-list entry to help identify its purpose within the organization. |
| org-slug-or-id | string | yes | The organization identifier, either as a UUID or a slug in the form `vcs-slug/org-name`. For organizations using GitLab or GitHub App, use `circleci` as the vcs-slug and the organization ID (found in… |
| prefix | – | – | The URL prefix that defines which URL orb references are permitted; any orb reference URL beginning with this prefix will be allowed by this entry. |
No output schema declared.
No examples provided.
create_usage_export Create Usage Export Job ~181
Submits a job to export usage data for an organization within a specified date range. The export covers up to 31 days of data and can optionally include usage from shared organizations.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | The end date and time (inclusive) of the export range in ISO 8601 format. Must be no more than 31 days after the start date. |
| org_id | string | yes | The unique identifier of the organization for which the usage export will be generated. |
| shared_org_ids | array | – | A list of additional organization IDs whose usage data should be included in the export, useful for aggregating usage across shared or linked organizations. Order is not significant. |
| start | string | yes | The start date and time (inclusive) of the export range in ISO 8601 format. Must be no more than one year in the past. |
No output schema declared.
No examples provided.
create_webhook Create Webhook ~233
Creates an outbound webhook that listens for specified events and delivers payloads to a designated HTTPS URL. Supports TLS verification enforcement and HMAC payload signing for secure delivery.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | List of event types that will trigger this webhook; order is not significant and each item should be a valid event type string. |
| id | string | – | The UUID of the scope (e.g., a project) this webhook is associated with; currently only project IDs are supported. |
| name | string | – | Human-readable name to identify the webhook. |
| signing-secret | string | – | A secret string used to generate an HMAC hash of the outgoing payload, which is passed as a header so the receiver can verify authenticity. |
| type | string | – | The type of scope the provided ID refers to; currently only project-level scopes are supported. |
| url | string | – | The destination URL where webhook payloads will be delivered; must include the protocol prefix and only HTTPS is supported. |
| verify-tls | boolean | – | When set to true, enforces strict TLS certificate verification on the destination URL before delivering the webhook payload. |
No output schema declared.
No examples provided.
delete_checkout_key Delete Checkout Key ~155
Deletes a specific checkout key for a project using its MD5 or SHA256 fingerprint. SHA256 fingerprints must be URL-encoded before being passed as the fingerprint parameter.
| Name | Type | Req | Description |
|---|---|---|---|
| fingerprint | string | yes | The MD5 or SHA256 fingerprint of the SSH checkout key to delete. SHA256 fingerprints must be URL-encoded. |
| 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 (from Organization Set… |
No output schema declared.
No examples provided.
delete_context Delete Context ~59
Permanently deletes a context and all of its associated environment variables by context ID. This action is irreversible.
| Name | Type | Req | Description |
|---|---|---|---|
| context_id | string | yes | The unique identifier of the context to delete. Deleting a context will also remove all environment variables stored within it. |
No output schema declared.
No examples provided.
delete_context_environment_variable Delete Context Environment Variable ~92
Permanently removes a named environment variable from the specified context. This action cannot be undone and will immediately make the variable unavailable to pipelines using that context.
| Name | Type | Req | Description |
|---|---|---|---|
| context_id | string | yes | The unique identifier of the context from which the environment variable will be deleted. |
| env_var_name | string | yes | The exact name of the environment variable to delete, matching the name as it was originally stored in the context. |
No output schema declared.
No examples provided.
delete_context_restriction Delete Context Restriction ~86
Permanently removes a specific restriction (project, expression, or group) from a context. This action cannot be undone and immediately revokes the associated access control rule.
| Name | Type | Req | Description |
|---|---|---|---|
| context_id | string | yes | The unique identifier of the context from which the restriction will be deleted. |
| restriction_id | string | yes | The unique identifier of the specific restriction to delete within the given context. |
No output schema declared.
No examples provided.
delete_env_var Delete Environment Variable ~151
Permanently deletes a specific environment variable from a CircleCI project. This action is irreversible and immediately removes the variable from the project's configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The exact name of the environment variable to delete, matching the variable's name as it appears in the project's environment variable settings. |
| project-slug | string | yes | The project slug uniquely identifying the target 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 Orga… |
No output schema declared.
No examples provided.
delete_group Delete Group ~84
Permanently deletes a group from a standalone organization, removing all its members and revoking any role grants associated with the group.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | The unique UUID identifier of the group to delete. All members and associated role grants will be removed upon deletion. |
| org_id | string | yes | The unique opaque identifier of the organization that contains the group to be deleted. |
No output schema declared.
No examples provided.
delete_org_oidc_claims Delete Organization OIDC Claims ~105
Deletes one or more custom OIDC identity token claims configured at the organization level. Supports removing the 'audience' and/or 'ttl' claim overrides.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | string | yes | Comma-separated list of custom OIDC claim names to delete. Valid values are 'audience' and 'ttl'; multiple values may be combined in a single request. |
| orgID | string | yes | The unique identifier of the organization whose custom OIDC claims will be deleted. |
No output schema declared.
No examples provided.
delete_organization Delete Organization ~110
Permanently deletes an organization and all associated projects and build data. This action is irreversible and will remove all resources tied to the organization.
| Name | Type | Req | Description |
|---|---|---|---|
| org-slug-or-id | string | yes | The unique identifier for the organization, either as a UUID or a VCS-prefixed slug in the format `vcs-slug/org-name`. For organizations using GitLab or GitHub App, use `circleci` as the VCS slug and… |
No output schema declared.
No examples provided.
delete_otlp_exporter Delete OTLP Exporter ~60
Permanently deletes an OTLP exporter configuration by its unique identifier. This is an experimental feature and the behavior may change in future releases.
| Name | Type | Req | Description |
|---|---|---|---|
| otel_exporter_id | string | yes | The unique identifier of the OTLP exporter configuration to delete. |
No output schema declared.
No examples provided.
delete_pipeline_definition Delete Pipeline Definition ~80
Permanently deletes a pipeline definition from a project. Currently only supported for pipeline definitions using GitHub App or Bitbucket Data Center as the config source provider.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_definition_id | string | yes | The unique opaque identifier of the pipeline definition to delete. |
| project_id | string | yes | The unique opaque identifier of the project containing the pipeline definition to delete. |
No output schema declared.
No examples provided.
delete_project Delete Project ~114
Permanently deletes a project from CircleCI using its unique project slug. This action is irreversible and removes all associated project data.
| 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.
delete_project_oidc_claims Delete Project OIDC Claims ~122
Deletes one or more custom claims from the OIDC identity token configuration at the project level. Only the 'audience' and 'ttl' claims are eligible for deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | string | yes | Comma-separated list of custom claim names to delete. Valid values are 'audience' and 'ttl'; multiple values may be combined in a single request. |
| orgID | string | yes | Unique identifier of the organization that owns the project. |
| projectID | string | yes | Unique identifier of the project whose OIDC custom claims will be deleted. |
No output schema declared.
No examples provided.
delete_schedule Delete Schedule ~55
Permanently deletes a 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 delete, in UUID format. |
No output schema declared.
No examples provided.
delete_trigger Delete Trigger ~84
Permanently deletes a trigger from the specified project. Supported only for triggers with an event source provider of GitHub OAuth, GitHub App, Bitbucket Data Center, or webhook.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The unique opaque identifier of the project from which the trigger will be deleted. |
| trigger_id | string | yes | The unique opaque identifier of the trigger to be deleted. |
No output schema declared.
No examples provided.
delete_url_orb_allow_list_entry Delete URL Orb Allow List Entry ~145
Removes a specific entry from the organization's URL orb allow-list by its unique ID. Use this to revoke previously permitted URLs from the allow-list.
| Name | Type | Req | Description |
|---|---|---|---|
| allow-list-entry-id | string | yes | The UUID of the URL orb allow-list entry to remove. This uniquely identifies the specific allow-list entry to be deleted. |
| org-slug-or-id | string | yes | The organization identifier, either as a UUID or a slug in the format `vcs-slug/org-name`. For GitLab or GitHub App projects, use `circleci` as the `vcs-slug` and provide the organization ID (found i… |
No output schema declared.
No examples provided.
delete_webhook Delete Webhook ~54
Permanently deletes an outbound webhook, stopping all future event deliveries to its configured endpoint. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook-id | string | yes | The unique identifier of the outbound webhook to delete, provided as a UUID. |
No output schema declared.
No examples provided.
get_checkout_key Get Checkout Key ~162
Retrieves a specific checkout key for a project using its MD5 or SHA256 fingerprint. SHA256 fingerprints must be URL-encoded before being passed as the fingerprint parameter.
| Name | Type | Req | Description |
|---|---|---|---|
| fingerprint | string | yes | The SSH key fingerprint used to uniquely identify the checkout key, accepted in either MD5 or SHA256 format. SHA256 fingerprints must be URL-encoded. |
| project-slug | string | yes | The project slug identifying the target 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… |
No output schema declared.
No examples provided.
get_component Get Component ~63
Retrieves the full details of a deployed component by its unique identifier. Use this to inspect configuration, status, or metadata for a specific component.
| Name | Type | Req | Description |
|---|---|---|---|
| component_id | string | yes | The unique opaque identifier of the component to retrieve, as returned when the component was created or listed. |
No output schema declared.
No examples provided.
get_context Get Context ~56
Retrieves basic information about a specific context by its unique identifier. Use this to look up context details when you have a known context ID.
| Name | Type | Req | Description |
|---|---|---|---|
| context_id | string | yes | The unique identifier of the context to retrieve, provided as a UUID. |
No output schema declared.
No examples provided.
get_current_user Get Current User ~33
Retrieves profile and account information for the currently authenticated user. Useful for identifying who is signed in and accessing their associated details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_decision_log Get Decision Log ~109
Retrieves a specific decision audit log entry for a given owner and context. Use this to inspect the details and outcome of a previously recorded decision by its unique ID.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | The context scope under which the decision was recorded, used to namespace or categorize decisions for the given owner. |
| decisionID | string | yes | The unique identifier of the specific decision log entry to retrieve. |
| ownerID | string | yes | The unique identifier of the owner whose decision audit log is being retrieved. |
No output schema declared.
No examples provided.
get_decision_policy_bundle Get Decision Policy Bundle ~113
Retrieves the policy bundle associated with a specific decision log entry. Useful for auditing which policies were evaluated at the time a given decision was made.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | The policy context scope under which the decision was evaluated, used to namespace and organize policies. |
| decisionID | string | yes | The unique identifier of the decision log entry for which the associated policy bundle should be retrieved. |
| ownerID | string | yes | The unique identifier of the owner (organization or user) whose decision log is being queried. |
No output schema declared.
No examples provided.
get_env_var Get Environment Variable ~133
Retrieves the masked value of a specific environment variable for a given project. The returned value is masked for security purposes.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The exact name of the environment variable to retrieve, matching the name as defined in the project's environment variable settings. |
| 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… |
No output schema declared.
No examples provided.
get_environment Get Environment ~54
Retrieves detailed information about a specific deployment environment by its unique identifier. Use this to inspect environment configuration, status, or metadata for a known environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_id | string | yes | The unique UUID identifying the deployment environment to retrieve. |
No output schema declared.
No examples provided.
get_group Get Group ~65
Retrieves details for a specific group within an organization. Currently only supported for standalone organizations.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | The unique identifier of the group to retrieve, provided as a UUID. |
| org_id | string | yes | The unique opaque identifier of the organization that contains the group. |
No output schema declared.
No examples provided.
get_job_details Get Job Details ~132
Retrieves detailed information about a specific job within a project, including its status, timing, and configuration. Use this to inspect the outcome or metadata of a particular job run.
| Name | Type | Req | Description |
|---|---|---|---|
| job-number | – | yes | The unique numeric identifier of the job to retrieve details for. |
| project-slug | string | yes | Project slug identifying the target 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 organ… |
No output schema declared.
No examples provided.
get_org_summary Get Organization Summary ~144
Retrieves aggregated performance metrics and trends for an entire organization and each of its projects. Supports filtering by a specific reporting window and an optional subset of projects.
| Name | Type | Req | Description |
|---|---|---|---|
| org-slug | string | yes | The organization slug identifying the target org, combining the VCS provider slug and organization name separated by a forward slash (which may be URL-encoded). |
| project-names | object | – | An optional list of project names used to filter results to specific projects within the org. Provide the parameter multiple times to include multiple projects. |
| reporting-window | string | – | The time window over which summary metrics are calculated and trends are derived. Defaults to the last 90 days if not specified. |
No output schema declared.
No examples provided.
get_organization Get Organization ~133
Retrieves details for a specific organization by its slug or UUID. Supports organizations across GitHub, Bitbucket, and GitLab (via CircleCI VCS slug).
| Name | Type | Req | Description |
|---|---|---|---|
| org-slug-or-id | string | yes | The organization identifier, either as a UUID or a VCS slug in the format `vcs-slug/org-name` (e.g., `gh/` for GitHub, `bb/` for Bitbucket). For GitLab or GitHub App integrations, use `circleci` as t… |
No output schema declared.
No examples provided.
get_pipeline Get Pipeline ~49
Retrieves detailed information about a specific pipeline using its unique identifier. Returns the full pipeline configuration and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline-id | string | yes | The unique identifier of the pipeline to retrieve, provided as a UUID. |
No output schema declared.
No examples provided.
get_pipeline_by_number Get Pipeline by Number ~124
Retrieves a specific pipeline by its number within a given project. Returns full pipeline details including status, configuration, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline-number | – | yes | The sequential number assigned to the pipeline within the project, uniquely identifying it among all pipelines for that project. |
| project-slug | string | yes | The project slug identifying the target 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 th… |
No output schema declared.
No examples provided.
get_pipeline_config Get Pipeline Config ~67
Retrieves the full configuration for a specific pipeline by its unique ID. Useful for inspecting pipeline settings, stages, and parameters without modifying them.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline-id | string | yes | The unique identifier of the pipeline whose configuration you want to retrieve. Must be a valid UUID corresponding to an existing pipeline. |
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 PyPI package (mcparmory-circleci).
Is the com.mcparmory/circleci MCP server safe to use?
com.mcparmory/circleci scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.