Circleci
Inspect and manage CircleCI pipelines, workflows, and job metrics from your agent while you ship releases.
Overview
com.mcparmory/circleci is a MCP server for the Ship phase that manages CircleCI pipelines, workflows, and job metrics from your agent.
What is this MCP server?
- stdio MCP server version 1.0.4 (2025-12-11 schema) from mcparmory
- Run with uvx mcparmory-circleci or Docker ghcr.io/mcparmory/circleci:1.0.4
- Manage CI/CD pipelines and workflows across CircleCI projects
- Surface job metrics for triage and release readiness
- Fits indie repos that already standardize on CircleCI for deploy gates
- 2 packages: PyPI mcparmory-circleci (uvx) and OCI ghcr.io/mcparmory/circleci:1.0.4
- stdio transport
Community signal: 25 GitHub stars.
What problem does it solve?
Chasing failed CircleCI jobs in a separate dashboard slows solo builders who need to fix and ship from one workspace.
Who is it for?
Solo developers and tiny teams on CircleCI who want MCP access to pipelines and job metrics during release week.
Skip if: Shops on GitHub Actions only, or teams that want hosted CI replaced rather than API-connected.
What do I get? / Deliverables
After registration, your agent can query and manage CircleCI CI/CD state alongside your codebase.
- Live MCP connection to CircleCI projects at server version 1.0.4
- Agent-driven pipeline and workflow management
- Job metrics visibility for ship-time triage
Recommended MCP Servers
Journey fit
CircleCI belongs on Ship when you are validating releases, debugging failed jobs, and keeping CI green before and after launch. Launch under Ship is the shelf for release-oriented CI/CD control—pipelines and workflow metrics tied to getting builds out the door.
How it compares
CircleCI MCP bridge, not a generic test runner skill or pipeline YAML generator.
Common Questions / FAQ
Who is com.mcparmory/circleci for?
Builders who deploy with CircleCI and use Claude Code, Cursor, or Codex to debug workflows and track job metrics via MCP.
When should I use com.mcparmory/circleci?
Use it in Ship when pipelines fail, before a release, or when you need workflow and metrics context without leaving the agent.
How do I add com.mcparmory/circleci to my agent?
Configure stdio MCP with uvx mcparmory-circleci or ghcr.io/mcparmory/circleci:1.0.4, set your CircleCI API token, and reload the client.