Loading...
The CircleCI MCP server enables interaction with CircleCI pipelines and resources using natural language via the Model Context Protocol.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
The CircleCI MCP server enables interaction with CircleCI pipelines and resources using natural language via the Model Context Protocol.
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.
Performance is primarily limited by the CircleCI API's response times and the network latency between the MCP server and the CircleCI API endpoint. Large log retrievals may take longer.
Cost is primarily determined by CircleCI's pricing model, which may be based on usage (e.g., build minutes). Excessive or unnecessary API calls initiated through the MCP server could increase costs.
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)
}
}
}
}CIRCLECI_TOKENCIRCLECI_BASE_URLget_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.
API Key
hybrid
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.
Autonomy is governed by the permissions associated with the CircleCI API token. Ensure the token has appropriate, limited scope to minimize potential damage from automated actions.
Production Tip
Monitor the usage of the CircleCI API token and set up alerts for unusual activity to detect potential security breaches or performance issues.
It allows you to interact with CircleCI using natural language commands through the Model Context Protocol.
You need to provide a CircleCI API token with the necessary permissions.
You can trigger pipelines, retrieve logs, cancel pipelines, and approve workflows, among other things.
No, you should protect your API token and avoid exposing it in public repositories or insecure environments. Use environment variables or secure configuration management.
Yes, by using a CircleCI API token with limited scope and permissions.
An attacker could use the token to perform unauthorized actions on your CircleCI account. Revoke the token immediately and generate a new one.
Auditing capabilities depend on the MCP client and CircleCI's own audit logs. The MCP server itself may not provide detailed logging.