Buildkite MCP Server
用于 Buildkite 集成的模型上下文协议 (MCP) 服务器
Drew-Goddyn
README
Buildkite MCP 服务器
一个通过模型上下文协议 (MCP) 从 Buildkite 检索信息的微服务。
设置
- 克隆此仓库
- 运行
npm install
- 设置
BUILDKITE_ACCESS_TOKEN
环境变量 - 使用
node index.js
启动服务器
与 Cursor 一起使用 (MCP 集成)
要将此服务器添加到 Cursor,您需要在 ~/.cursor/config/mcp.json
文件中进行配置:
{
"mcpServers": {
"buildkite": {
"command": "npx",
"args": [
"-y",
"@drew-goddyn/buildkite-mcp"
],
"env": {
"BUILDKITE_ACCESS_TOKEN": "your-buildkite-access-token"
}
}
}
}
通过此配置:
- 您无需手动安装或运行服务器
- Cursor 将根据需要自动启动和停止服务器
- 将
your-buildkite-access-token
替换为您实际的 Buildkite API 令牌
更新配置后,重启 Cursor 以应用更改。
MCP 端点
列出组织
POST /mcp_buildkite_list_organizations
请求体:
{
"access_token": "optional-if-set-in-env"
}
响应:
[
{
"id": "org-id",
"name": "Organization Name",
"slug": "organization-slug"
}
]
列出流水线
POST /mcp_buildkite_list_pipelines
请求体:
{
"organization": "my-org",
"access_token": "optional-if-set-in-env"
}
响应:
[
{
"id": "pipeline-id",
"name": "Pipeline Name",
"slug": "pipeline-slug"
}
]
列出构建
POST /mcp_buildkite_list_builds
请求体:
{
"organization": "my-org",
"pipeline": "my-pipeline",
"access_token": "optional-if-set-in-env",
"branch": "main",
"state": "failed",
"per_page": 10,
"page": 1
}
响应:
[
{
"id": "build-id",
"number": 123,
"state": "failed"
}
]
获取构建详情
POST /mcp_buildkite_get_build
请求体:
{
"organization": "my-org",
"pipeline": "my-pipeline",
"build_number": 123,
"access_token": "optional-if-set-in-env"
}
响应:
{
"id": "build-id",
"number": 123,
"jobs": [
{
"id": "job-id",
"name": "Job Name",
"state": "failed"
}
]
}
列出所有任务
POST /mcp_buildkite_list_jobs
请求体:
{
"organization": "my-org",
"pipeline": "my-pipeline",
"build_number": 123,
"access_token": "optional-if-set-in-env"
}
响应:
[
{
"id": "job-id",
"name": "Job Name",
"state": "failed"
}
]
列出失败的任务
POST /mcp_buildkite_list_failed_jobs
请求体:
{
"organization": "my-org",
"pipeline": "my-pipeline",
"build_number": 123,
"access_token": "optional-if-set-in-env"
}
响应:
[
{
"id": "01234567-89ab-cdef-0123-456789abcdef",
"name": "Test Job",
"state": "failed",
"web_url": "https://buildkite.com/my-org/my-pipeline/builds/123#01234567-89ab-cdef-0123-456789abcdef"
}
]
列出任务规范失败
POST /mcp_buildkite_list_job_spec_failures
请求体:
{
"organization": "my-org",
"pipeline": "my-pipeline",
"build_number": 123,
"job_id": "01234567-89ab-cdef-0123-456789abcdef",
"access_token": "optional-if-set-in-env"
}
响应:
[
{
"type": "RSpec",
"spec": "./spec/path/to/file_spec.rb:123",
"message": "Expected result to be X but got Y"
}
]
获取任务日志
POST /mcp_buildkite_get_job_log
请求体:
{
"organization": "my-org",
"pipeline": "my-pipeline",
"build_number": 123,
"job_id": "01234567-89ab-cdef-0123-456789abcdef",
"access_token": "optional-if-set-in-env",
"limit": 100 // optional, defaults to all content
}
响应:
{
"content": "...log content...",
"size": 12345,
"format": "raw"
}
从构建 URL 列出失败的 Specs
POST /mcp_buildkite_list_failed_specs
请求体:
{
"build_url": "https://buildkite.com/my-org/my-pipeline/builds/123",
"access_token": "optional-if-set-in-env"
}
响应:
{
"build_url": "https://buildkite.com/my-org/my-pipeline/builds/123",
"failed_job_count": 2,
"jobs": [
{
"id": "01234567-89ab-cdef-0123-456789abcdef",
"name": "Test Job 1",
"web_url": "https://buildkite.com/my-org/my-pipeline/builds/123#01234567-89ab-cdef-0123-456789abcdef",
"failures": [
{
"spec": "./spec/path/to/file_spec.rb:123",
"message": "Expected result to be X but got Y"
}
]
},
{
"id": "fedcba98-7654-3210-fedc-ba9876543210",
"name": "Test Job 2",
"web_url": "https://buildkite.com/my-org/my-pipeline/builds/123#fedcba98-7654-3210-fedc-ba9876543210",
"failures": []
}
],
"failures": [
{
"job_id": "01234567-89ab-cdef-0123-456789abcdef",
"job_name": "Test Job 1",
"job_url": "https://buildkite.com/my-org/my-pipeline/builds/123#01234567-89ab-cdef-0123-456789abcdef",
"spec": "./spec/path/to/file_spec.rb:123",
"message": "Expected result to be X but got Y"
}
]
}
重试任务
POST /mcp_buildkite_retry_job
请求体:
{
"organization": "my-org",
"pipeline": "my-pipeline",
"build_number": 123,
"job_id": "01234567-89ab-cdef-0123-456789abcdef",
"access_token": "optional-if-set-in-env"
}
响应:
{
"id": "job-id",
"state": "scheduled"
}
列出流水线构建失败
POST /mcp_buildkite_list_pipeline_build_failures
请求体:
{
"organization": "my-org",
"pipeline": "my-pipeline",
"state": "finished",
"per_page": 10,
"page": 1,
"access_token": "optional-if-set-in-env"
}
响应:
[
{
"build_number": 123,
"build_url": "https://buildkite.com/my-org/my-pipeline/builds/123",
"failed_jobs": [
{
"name": "Test Job",
"url": "https://buildkite.com/my-org/my-pipeline/builds/123#01234567-89ab-cdef-0123-456789abcdef"
}
]
}
]
环境变量
BUILDKITE_ACCESS_TOKEN
: 您的 Buildkite API 令牌,具有读取权限PORT
: (可选) 运行服务器的端口 (默认: 63330)
错误处理
当出现问题时,服务器会返回适当的 HTTP 状态代码和错误消息:
400
: Bad Request - 缺少或无效的参数401
: Unauthorized - 无效或缺失的访问令牌404
: Not Found - 找不到资源500
: Internal Server Error - 服务器端错误
推荐服务器
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
MCP Package Docs Server
促进大型语言模型高效访问和获取 Go、Python 和 NPM 包的结构化文档,通过多语言支持和性能优化来增强软件开发。
Claude Code MCP
一个实现了 Claude Code 作为模型上下文协议(Model Context Protocol, MCP)服务器的方案,它可以通过标准化的 MCP 接口来使用 Claude 的软件工程能力(代码生成、编辑、审查和文件操作)。
@kazuph/mcp-taskmanager
用于任务管理的模型上下文协议服务器。它允许 Claude Desktop(或任何 MCP 客户端)在基于队列的系统中管理和执行任务。
mermaid-mcp-server
一个模型上下文协议 (MCP) 服务器,用于将 Mermaid 图表转换为 PNG 图像。
Jira-Context-MCP
MCP 服务器向 AI 编码助手(如 Cursor)提供 Jira 工单信息。

Linear MCP Server
一个模型上下文协议(Model Context Protocol)服务器,它与 Linear 的问题跟踪系统集成,允许大型语言模型(LLM)通过自然语言交互来创建、更新、搜索和评论 Linear 问题。

Sequential Thinking MCP Server
这个服务器通过将复杂问题分解为顺序步骤来促进结构化的问题解决,支持修订,并通过完整的 MCP 集成来实现多条解决方案路径。
Curri MCP Server
通过管理文本笔记、提供笔记创建工具以及使用结构化提示生成摘要,从而实现与 Curri API 的交互。