Circleci MCP server

Read from the package source without running it. The installed server may list more.

• add_context_restriction

  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.

• approve_workflow_job

  Approves a pending approval job within a specified workflow, allowing the workflow to continue past the approval gate.

• cancel_jobwrite action

  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.

• cancel_job_by_numberwrite action

  Cancels a running job in a specified project using its job number. Useful for stopping unwanted or erroneous builds mid-execution.

• cancel_workflowwrite action

  Cancels a currently running workflow, halting any further execution. Use this to stop a workflow that is in progress before it completes naturally.

• continue_pipeline

  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.

• create_checkout_keywrite action

  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.

• create_contextwrite action

  Creates a new named context within a specified organization, allowing you to group and manage related environment variables or secrets.

• create_env_varwrite action

  Creates a new environment variable for a specified CircleCI project, making it available to pipelines and jobs running within that project.

• create_groupwrite action

  Creates a new group within a standalone organization, allowing members and resources to be organized under a named group. Only supported for standalone organizations.

• create_organizationwrite action

  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.

• create_pipeline_definitionwrite action

  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.

• create_pipeline_triggerwrite action

  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.

• create_projectwrite action

  Creates a new project within the specified organization. Works across all organization types including GitHub, GitLab, and CircleCI-managed organizations.

• create_schedulewrite action

  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.

• create_url_orb_allow_list_entrywrite action

  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.

• create_usage_exportwrite action

  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.

• create_webhookwrite action

  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.

• delete_checkout_keywrite action

  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.

• delete_contextwrite action

  Permanently deletes a context and all of its associated environment variables by context ID. This action is irreversible.

• delete_context_environment_variablewrite action

  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.

• delete_context_restrictionwrite action

  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.

• delete_env_varwrite action

  Permanently deletes a specific environment variable from a CircleCI project. This action is irreversible and immediately removes the variable from the project's configuration.

• delete_groupwrite action

  Permanently deletes a group from a standalone organization, removing all its members and revoking any role grants associated with the group.

• delete_org_oidc_claimswrite action

  Deletes one or more custom OIDC identity token claims configured at the organization level. Supports removing the 'audience' and/or 'ttl' claim overrides.

• delete_organizationwrite action

  Permanently deletes an organization and all associated projects and build data. This action is irreversible and will remove all resources tied to the organization.

• delete_pipeline_definitionwrite action

  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.

• delete_projectwrite action

  Permanently deletes a project from CircleCI using its unique project slug. This action is irreversible and removes all associated project data.

• delete_project_oidc_claimswrite action

  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.

• delete_schedulewrite action

  Permanently deletes a pipeline schedule by its unique ID. Only available for schedules associated with GitHub OAuth or Bitbucket Cloud pipeline definitions.

• delete_triggerwrite action

  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.

• delete_url_orb_allow_list_entrywrite action

  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.

• delete_webhookwrite action

  Permanently deletes an outbound webhook, stopping all future event deliveries to its configured endpoint. This action cannot be undone.

• get_checkout_key

  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.

• get_context

  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.

• get_current_user

  Retrieves profile and account information for the currently authenticated user. Useful for identifying who is signed in and accessing their associated details.

• get_decision_log

  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.

• get_decision_policy_bundle

  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.

• get_env_var

  Retrieves the masked value of a specific environment variable for a given project. The returned value is masked for security purposes.

• get_group

  Retrieves details for a specific group within an organization. Currently only supported for standalone organizations.

• get_job_details

  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.

• get_org_summary

  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.

• get_organization

  Retrieves details for a specific organization by its slug or UUID. Supports organizations across GitHub, Bitbucket, and GitLab (via CircleCI VCS slug).

• get_pipeline

  Retrieves detailed information about a specific pipeline using its unique identifier. Returns the full pipeline configuration and metadata.

• get_pipeline_by_number

  Retrieves a specific pipeline by its number within a given project. Returns full pipeline details including status, configuration, and metadata.

• get_pipeline_config

  Retrieves the full configuration for a specific pipeline by its unique ID. Useful for inspecting pipeline settings, stages, and parameters without modifying them.

• get_pipeline_definition

  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.

• get_pipeline_values

  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.

• get_policy_bundle

  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.

• get_project

  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.

• get_project_oidc_claims

  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.

• get_project_settings

  Retrieves the advanced settings for a specified CircleCI project, returning each setting with a boolean indicating whether it is enabled or disabled.

• get_project_workflow_summary

  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.

• get_schedule

  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.

• get_trigger

  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.

• get_usage_export_job

  Retrieves the status and details of a specific usage export job for an organization, including download information once the export is complete.

• get_user

  Retrieves profile and account information for a specific user. Use this to look up user details by their unique identifier.

• get_webhook

  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.

• get_workflow

  Retrieves summary fields for a specific workflow by its unique identifier. Useful for checking workflow metadata such as name, status, and configuration details.

• get_workflow_summary

  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.

• get_workflow_test_metrics

  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.

• list_checkout_keys

  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.

• list_collaborations

  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.

• list_context_environment_variables

  Retrieves a list of environment variables defined within a specified context, returning metadata such as names but excluding their values for security.

• list_context_restrictions

  Retrieves all project and expression restrictions associated with a specific context. Returns the complete list of restrictions currently applied to the given context.

• list_contexts

  Retrieves all contexts belonging to a specified organization or owner, enabling management of shared environment variables and secrets across projects.

• list_decision_logs

  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.

• list_env_vars

  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.

• list_flaky_tests

  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.

• list_job_artifacts

  Retrieves all artifacts produced by a specific job in a CircleCI project. Useful for accessing build outputs such as test reports, binaries, or logs.

• list_job_tests

  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.

• list_job_timeseries

  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.

• list_my_pipelines

  Retrieves all pipelines for a specified project that were triggered by the authenticated user. Returns results as a sequence ordered by trigger time.

• list_org_oidc_custom_claims

  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.

• list_organization_groups

  Retrieves all groups belonging to a specified organization. Supports pagination to control the number of results returned per page.

• list_pipeline_definition_triggers

  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.

• list_pipeline_definitions

  Retrieves all pipeline definitions associated with a specified project. Pipeline definitions describe the structure and configuration of pipelines available within the project.

• list_pipeline_workflows

  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.

• list_pipelines

  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.

• list_project_branches

  Retrieves all branches currently tracked within Insights for a specified project. Returns up to 5,000 branches, optionally scoped to a specific workflow.

• list_project_pipelines

  Retrieves all pipelines for a specified project, optionally filtered by branch. Useful for monitoring CI/CD activity and pipeline history across a project.

• list_project_schedules

  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.

• list_url_orb_allow_list_entries

  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.

• list_webhooks

  Retrieves all outbound webhooks associated with a given scope. Currently supports project-level scoping by providing a project ID.

• list_workflow_job_metrics

  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.

• list_workflow_jobs

  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.

• list_workflow_metrics

  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.

• list_workflow_runs

  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.

• rerun_workflow

  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.

• rollback_project

  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.

• set_context_environment_variablewrite action

  Creates or updates a named environment variable within a specified context. Returns metadata about the variable after the operation, excluding its value.

• trigger_pipeline

  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.

• trigger_pipeline_runwrite action

  Trigger a new pipeline run for a project using a specific pipeline definition. Supports GitHub, Bitbucket, and CircleCI integrations (GitLab not supported).

• update_org_oidc_claimswrite action

  Creates or updates org-level custom claims on OIDC identity tokens for the specified organization. Use this to configure audience restrictions and token time-to-live settings.

• update_pipeline_definitionwrite action

  Updates an existing pipeline definition for a project, allowing changes to its name, description, config file path, or version control source settings. Currently supported only for pipeline definitions using GitHub App or Bitbucket Data Center as the config source provider.

• update_project_oidc_claimswrite action

  Creates or updates project-level custom claims on OIDC identity tokens for the specified project. Use this to configure audience restrictions and token time-to-live at the project scope.

• update_project_settingswrite action

  Updates one or more advanced settings for a CircleCI project, such as build behavior, fork policies, SSH access, and GitHub status reporting. Only the settings fields provided in the request body will be modified.

• update_schedulewrite action

  Updates an existing pipeline schedule by ID and returns the updated schedule. Only available for schedules associated with GitHub OAuth or Bitbucket Cloud pipeline definitions; use the Update Trigger endpoint for GitHub App pipeline definitions.

• update_triggerwrite action

  Update configuration for an existing pipeline trigger on a project. Currently supported for triggers with a provider of `github_oauth`, `github_app`, `bitbucket_dc`, or `webhook`.

• update_webhookwrite action

  Updates the configuration of an existing outbound webhook, allowing changes to its name, target URL, triggered events, signing secret, and TLS verification behavior. Only fields provided in the request will be updated.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 138 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 55% of 1,119 Developer tools servers

Tools

100

the typical Developer tools server has 7

Tools that change things

39%

typical: 5%. Fewer write tools means less an agent can break

GitHub stars

31

more than 90% of 855 Developer tools servers

Downloads a week

151

more than 66% of 436 Developer tools servers with a package

Circleci: common questions

Is Circleci MCP server safe?

Mostly: it is graded B (80/100). Read the Circleci safety report

How do I install Circleci?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Circleci need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Circleci maintained?

The last commit was 176 days ago (2026-05-12). The latest release is v1.0.4.

What can I use instead of Circleci?

Servers from other publishers that do the same job: GitLab MCP Server, Gitlab MCP server and Zuul MCP server. Compare all Circleci alternatives.

How does Circleci compare with other Developer tools MCP servers?

safety score 80/100 (higher than 55% of 1,119 Developer tools servers); tools 100 (the typical Developer tools server has 7); tools that change things 39% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.