zed -buildkite

This MCP server provides an integration that lets you interact with Buildkite from the Zed editor via the MCP framework. It enables you to view Buildkite pipelines and recent builds, inspect individual jobs and their logs, and download build artifacts directly from within Zed. To use it, install the extension in Zed and configure your Buildkite API token in the extension settings. The server will manage authentication and communication with the Buildkite API, exposing the relevant capabilities to your MCP-enabled workflows and AI-assisted queries in Zed. Typical queries might include requesting recent builds for a pipeline, listing pipelines in your organization, or pulling logs for a failed job. The extension is designed to work seamlessly with Zed’s AI features, enabling natural language queries that translate into Buildkite actions.

Prerequisites:

• Node.js and npm installed on your machine
• An active Buildkite API token with appropriate scopes

Step 1: Install the MCP server package

• Using npm (recommended): npm install -g mcncl-zed-mcp-server-buildkite

Step 2:Set up environment variable for Buildkite token

• Obtain your Buildkite API token from Buildkite (Settings > Access Tokens).
• Ensure the token is available to the server, e.g.: export BUILDKITE_API_TOKEN=your-buildkite-token-here

Step 3: Run the MCP server

• Start the server (example using npx as configured by the MCP): npx -y mcncl-zed-mcp-server-buildkite

Step 4: Connect from Zed

• In Zed, install the MCP extension (Buildkite MCP Extension).
• Add a context server entry that points to the running MCP server if required by your setup, and provide the Buildkite API token in the extension settings (or ensure the environment variable is accessible to the server process).

Note: If you prefer a persistent process, consider wrapping the start command in a process manager (e.g., systemd, pm2) and ensure the BUILDKITE_API_TOKEN environment variable is set in the service environment.

Tips and considerations:

• Keep your Buildkite API token secure; avoid placing it in code or public settings.
• The MCP server expects standard Buildkite API scopes required for listing pipelines, builds, jobs, and artifacts.
• If you encounter authentication errors, double-check that the token has the required permissions and that the environment variable is available to the running process.
• For large organizations, consider paginating API requests and caching commonly accessed data to improve responsiveness in the MCP client.
• If the extension supports multiple MCP servers, ensure unique server names in your configuration to avoid conflicts.