mcp-server-circleci

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CIRCLECI_TOKENYesYour CircleCI API token with read access to your CircleCI projects
CIRCLECI_BASE_URLNoThe base URL for CircleCI APIhttps://circleci.com

Schema

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Tools

Functions exposed to the LLM to take actions

NameDescription
get_build_failure_logs
This tool helps debug CircleCI build failures by retrieving failure logs. Input options (EXACTLY ONE of these two options must be used): Option 1 - Direct URL (provide ONE of these): - projectURL: The URL of the CircleCI project in any of these formats: * Project URL: https://app.circleci.com/pipelines/gh/organization/project * Pipeline URL: https://app.circleci.com/pipelines/gh/organization/project/123 * Workflow URL: https://app.circleci.com/pipelines/gh/organization/project/123/workflows/abc-def * Job URL: https://app.circleci.com/pipelines/gh/organization/project/123/workflows/abc-def/jobs/xyz Option 2 - Project Detection (ALL of these must be provided together): - workspaceRoot: The absolute path to the workspace root - gitRemoteURL: The URL of the git remote repository - branch: The name of the current branch IMPORTANT: - Never call this tool with incomplete parameters - If using Option 1, the URLs MUST be provided by the user - do not attempt to construct or guess URLs - If using Option 2, ALL THREE parameters (workspaceRoot, gitRemoteURL, branch) must be provided - If neither option can be fully satisfied, ask the user for the missing information before making the tool call
find_flaky_tests
This tool retrieves information about flaky tests in a CircleCI project. The agent receiving this output MUST analyze the flaky test data and implement appropriate fixes based on the specific issues identified. Input options (EXACTLY ONE of these two options must be used): Option 1 - Direct URL (provide ONE of these): - projectURL: The URL of the CircleCI project in any of these formats: * Project URL: https://app.circleci.com/pipelines/gh/organization/project * Pipeline URL: https://app.circleci.com/pipelines/gh/organization/project/123 * Workflow URL: https://app.circleci.com/pipelines/gh/organization/project/123/workflows/abc-def * Job URL: https://app.circleci.com/pipelines/gh/organization/project/123/workflows/abc-def/jobs/xyz Option 2 - Project Detection (ALL of these must be provided together): - workspaceRoot: The absolute path to the workspace root - gitRemoteURL: The URL of the git remote repository IMPORTANT: - Never call this tool with incomplete parameters - If using Option 1, the URLs MUST be provided by the user - do not attempt to construct or guess URLs - If using Option 2, BOTH parameters (workspaceRoot, gitRemoteURL) must be provided - If neither option can be fully satisfied, ask the user for the missing information before making the tool call
ID: 65ardm1kp6