Loading...
npx -y @smithery/cli install @CircleCI-Public/mcp-server-circleci --client claude{
"mcpServers": {
"circleci-mcp-server": {
"command": "npx",
"args": ["-y", "@circleci/mcp-server-circleci@latest"],
"env": {
"CIRCLECI_TOKEN": "your-circleci-token",
"CIRCLECI_BASE_URL": "https://circleci.com", // Optional - required for on-prem customers only
"MAX_MCP_OUTPUT_LENGTH": "50000" // Optional - maximum output length for MCP responses (default: 50000)
}
}
}
}get_pipeline_logsRetrieves logs from a specified CircleCI pipeline.
Read-only operation; retrieves existing logs.
trigger_pipelineTriggers a new CircleCI pipeline run.
Initiates a new pipeline execution, potentially consuming resources.
cancel_pipelineCancels a running CircleCI pipeline.
Stops a running pipeline, potentially interrupting workflows.
approve_workflowApproves a pending CircleCI workflow.
Approves a workflow, potentially triggering further actions.
list_pipelinesLists available CircleCI pipelines.
Read-only operation; lists existing pipelines.
The CircleCI MCP server's safety depends on the security of the CircleCI API token. While it offers some configuration options to limit exposure, the potential for write operations means careful token management is crucial. Using a token with limited scope and monitoring its usage are recommended.