What are the requirements?
You need a Buildkite API token, which can be created from your Buildkite account settings.
@mcncl
基本情報
Buildkite Integration for Zed - Access your Buildkite CI/CD pipelines and builds directly from your editor
ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
The Buildkite MCP Extension for Zed integrates Buildkite CI/CD with the Zed editor using the Model Context Protocol (MCP). It allows developers to view and interact with Buildkite pipelines, builds, jobs, and artifacts directly within Zed.
Install the extension from the Zed marketplace, then configure your Buildkite API token in Zed’s settings using a JSON block. The extension automatically handles all server and connection details. Example queries include “Show me recent builds for my pipeline” or “Display logs for my failed job.”
You need a Buildkite API token, which can be created from your Buildkite account settings.
Add a `buildkite_api_token` field under the server’s settings in Zed’s `context_servers` configuration JSON.
You can view pipelines and builds, inspect job logs, and download build artifacts—all within Zed.
Yes, it is designed specifically for the Zed editor and uses MCP to integrate with Buildkite.
All data is fetched from the Buildkite API using your provided API token.

Verified distributed compute for humans, applications, and agents. Submit Blender, Octane, and video workloads, route them across qualified GPUs, track asynchronous execution, download finished artifacts, and verify FARP

Build custom POS apps with your AI agent. Final's MCP server lets developers scaffold checkout flows, adapt vetted screen blueprints for counter POS, self-checkout kiosks, restaurant ordering and payment terminals, previ
OrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.
MCP server that lets Claude Code, Cursor or Codex ask you for API keys on a local page and write them to .env. The agent only ever sees key names.

Agent-Native Terminal
コメント