Integration

CircleCI integration

Continuous integration and deployment platform API. Manage pipelines, workflows, jobs, and build artifacts. Trigger builds, monitor status, retrieve test results, and automate CI/CD workflows. Essential for DevOps automation, build monitoring, and deployment pipelines.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in CircleCI.Built from the 39 CircleCI tools below, on the connection you add once.

Common CircleCI use cases

  • Variable audit
  • Secret rotation
  • Secret management
  • Project configuration
  • Context inspection
  • Pipeline inspection
  • Variable cleanup
  • Build progress
  • Security maintenance
  • Security cleanup

What you can do with CircleCI

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Context, 7 operations

  • add_context_env_varAdd context env varPUTAdds or updates an environment variable in a context.
  • create_contextCreate contextPOSTCreates a new context for an organization.
  • delete_contextDelete contextDELETEDeletes a context and all its environment variables.
  • delete_context_env_varDelete context env varDELETERemoves an environment variable from a context.
  • get_contextGet contextGETRetrieves a context by its ID.
  • list_context_env_varsList context env varsGETLists environment variables in a context (names only, not values).
  • list_contextsList contextsGETLists all contexts (shared env var groups) for an organization.

Pipeline, 5 operations

  • get_pipelineGet pipelineGETRetrieves details for a specific CircleCI pipeline.
  • get_pipeline_configGet pipeline configGETRetrieves the compiled configuration for a pipeline.
  • list_my_pipelinesList my pipelinesGETLists pipelines across all followed projects in an organization.
  • list_project_pipelinesList project pipelinesGETLists pipelines for a CircleCI project with filtering options.
  • trigger_pipelineTrigger pipelinePOSTTriggers a new pipeline run for a CircleCI project.

Schedule, 5 operations

  • create_scheduleCreate schedulePOSTCreates a new pipeline schedule trigger.
  • delete_scheduleDelete scheduleDELETEDeletes a pipeline schedule trigger.
  • get_scheduleGet scheduleGETRetrieves details for a specific pipeline schedule.
  • list_schedulesList schedulesGETLists all pipeline schedule triggers.
  • update_scheduleUpdate schedulePATCHUpdates an existing pipeline schedule trigger.

Webhook, 5 operations

  • create_webhookCreate webhookPOSTCreates an outbound webhook for CircleCI event notifications.
  • delete_webhookDelete webhookDELETEDeletes an outbound webhook.
  • get_webhookGet webhookGETRetrieves details for a specific webhook by ID.
  • list_webhooksList webhooksGETLists all outbound webhooks for a project or organization.
  • update_webhookUpdate webhookPUTUpdates an existing outbound webhook configuration.

Workflow, 5 operations

  • approve_jobApprove jobPOSTApproves a pending approval job in a workflow.
  • cancel_workflowCancel workflowPOSTCancels a running workflow and stops all its jobs.
  • get_pipeline_workflowsGet pipeline workflowsGETLists all workflows within a specific pipeline.
  • get_workflowGet workflowGETRetrieves details for a specific workflow.
  • rerun_workflowRerun workflowPOSTReruns a workflow from the beginning or from failed jobs.

Environment variable, 3 operations

  • create_project_env_varCreate project env varPOSTCreates a new environment variable for a project.
  • delete_project_env_varDelete project env varDELETEDeletes a project environment variable by name.
  • list_project_env_varsList project env varsGETLists all environment variables for a project (values masked).

Insights, 2 operations

  • get_flaky_testsGet flaky testsGETLists flaky tests for a project.
  • get_project_workflow_metricsGet project workflow metricsGETGets workflow metrics and performance data for a project.

User, 2 operations

  • get_current_userGet current userGETRetrieves the authenticated user's CircleCI profile.
  • get_userGet userGETRetrieves a user's profile by their ID.

Artifact, 1 operation

  • get_job_artifactsGet job artifactsGETLists artifacts produced by a specific job.

Job, 1 operation

  • get_workflow_jobsGet workflow jobsGETLists all jobs within a specific workflow.

Organization, 1 operation

  • get_collaborationsGet collaborationsGETLists organizations the authenticated user belongs to.

Project, 1 operation

  • get_projectGet projectGETRetrieves project information by project slug.

Test, 1 operation

  • get_job_testsGet job testsGETRetrieves test metadata for a specific job.

CircleCI API rate limits

  • 1,000 requests per minute

1000 req/min per user token for most endpoints (verified from CircleCI docs). Some endpoints have lower limits - e.g. usage report GET/POST: 10 req/hour per org. Throttling returns HTTP 429 with Retry-After header. Headers: X-RateLimit-Limit-<Second|Minute|Hour|Day>.

These are the limits CircleCI documents, not ones LiveContext measured. They can change and often depend on your plan, so check the CircleCI documentation for current values.

Use CircleCI from Claude Code, Cursor or Codex

Connect CircleCI in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its CircleCI operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect CircleCI

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect CircleCI once

    Add your CircleCI connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

CircleCI integration FAQ

What can you do with the CircleCI integration?

LiveContext exposes 39 operations on CircleCI, covering context, pipeline, schedule and webhook. Common uses include Variable audit, Secret rotation and Secret management.

What are the CircleCI API rate limits?

CircleCI documents 1,000 requests per minute. 1000 req/min per user token for most endpoints (verified from CircleCI docs). Some endpoints have lower limits - e.g. usage report GET/POST: 10 req/hour per org. Throttling returns HTTP 429 with Retry-After header. Headers: X-RateLimit-Limit-<Second|Minute|Hour|Day>. Limits are set by CircleCI and can depend on your plan.

Popular integrations

Browse the whole catalog