Buildkite MCP

🚀 Buildkite API Server Documentation

This server provides a series of interfaces to interact with the Buildkite platform, allowing you to perform various operations such as retrieving build information and retrying jobs. Below is a detailed description of all available interfaces.

🚀 Quick Start

This server offers a set of APIs to interact with the Buildkite platform. You can use these APIs to perform operations like getting build information and retrying jobs.

✨ Features

• Retrieve detailed build information.
• Retry jobs on the Buildkite platform.
• Get a list of failed builds in a specified pipeline.

📚 Documentation

🔍 Interface List

1. Retrieve Build Information

• Interface Name: /build-info
• Request Method: GET
• Parameters: build_url (Required)
• Response: Returns detailed information about the specified build, including job status and failure information.

2. Retry Job

• Interface Name: /retry-job
• Request Method: POST
• Request Body:

{
  "organization": "my-org",
  "pipeline": "my-pipeline", 
  "build_number": 123,
  "job_id": "01234567-89ab-cdef-0123-456789abcdef",
  "access_token": "your-token"
}

• Response: Returns the status of the retried job.

3. Retrieve Build Failure Information

• Interface Name: /build-failures
• Request Method: POST
• Request Body:

{
  "organization": "my-org",
  "pipeline": "my-pipeline", 
  "state": "finished",
  "per_page": 10,
  "page": 1,
  "access_token": "your-token"
}

• Response: Returns a list of failed builds in the specified pipeline, including job information for each build.

🛠️ Environment Variables

• BUILDKITE_ACCESS_TOKEN: Your Buildkite API token with read permissions.
• PORT (Optional): The port on which the server runs (Default: 63330).

🐞 Error Handling

The server returns appropriate HTTP status codes and error messages in case of errors:

• 400: Bad Request - Missing or invalid parameters.
• 401: Unauthorized - Invalid or missing access token.
• 404: Not Found - Resource not found.
• 500: Internal Server Error.