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.

LiveContext

All integrations

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.

39 toolsAPI keyAPI docs

Connect CircleCI How integrations work

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

PUTadd_context_env_var
Adds or updates an environment variable in a context.
POSTcreate_context
Creates a new context for an organization.
DELETEdelete_context
Deletes a context and all its environment variables.
DELETEdelete_context_env_var
Removes an environment variable from a context.
GETget_context
Retrieves a context by its ID.
GETlist_context_env_vars
Lists environment variables in a context (names only, not values).
GETlist_contexts
Lists all contexts (shared env var groups) for an organization.

Pipeline, 5 operations

GETget_pipeline
Retrieves details for a specific CircleCI pipeline.
GETget_pipeline_config
Retrieves the compiled configuration for a pipeline.
GETlist_my_pipelines
Lists pipelines across all followed projects in an organization.
GETlist_project_pipelines
Lists pipelines for a CircleCI project with filtering options.
POSTtrigger_pipeline
Triggers a new pipeline run for a CircleCI project.

Schedule, 5 operations

POSTcreate_schedule
Creates a new pipeline schedule trigger.
DELETEdelete_schedule
Deletes a pipeline schedule trigger.
GETget_schedule
Retrieves details for a specific pipeline schedule.
GETlist_schedules
Lists all pipeline schedule triggers.
PATCHupdate_schedule
Updates an existing pipeline schedule trigger.

Webhook, 5 operations

POSTcreate_webhook
Creates an outbound webhook for CircleCI event notifications.
DELETEdelete_webhook
Deletes an outbound webhook.
GETget_webhook
Retrieves details for a specific webhook by ID.
GETlist_webhooks
Lists all outbound webhooks for a project or organization.
PUTupdate_webhook
Updates an existing outbound webhook configuration.

Workflow, 5 operations

POSTapprove_job
Approves a pending approval job in a workflow.
POSTcancel_workflow
Cancels a running workflow and stops all its jobs.
GETget_pipeline_workflows
Lists all workflows within a specific pipeline.
GETget_workflow
Retrieves details for a specific workflow.
POSTrerun_workflow
Reruns a workflow from the beginning or from failed jobs.

Environment variable, 3 operations

POSTcreate_project_env_var
Creates a new environment variable for a project.
DELETEdelete_project_env_var
Deletes a project environment variable by name.
GETlist_project_env_vars
Lists all environment variables for a project (values masked).

Insights, 2 operations

GETget_flaky_tests
Lists flaky tests for a project.
GETget_project_workflow_metrics
Gets workflow metrics and performance data for a project.

User, 2 operations

GETget_current_user
Retrieves the authenticated user's CircleCI profile.
GETget_user
Retrieves a user's profile by their ID.

Artifact, 1 operation

GETget_job_artifacts
Lists artifacts produced by a specific job.

Job, 1 operation

GETget_workflow_jobs
Lists all jobs within a specific workflow.

Organization, 1 operation

GETget_collaborations
Lists organizations the authenticated user belongs to.

Project, 1 operation

GETget_project
Retrieves project information by project slug.

Test, 1 operation

GETget_job_tests
Retrieves 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

Create your workspace
Sign up free. Nothing to install.
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.
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.