zed-mcp-server-buildkite

Provides an MCP (Model Context Protocol) integration for Zed to browse and interact with Buildkite CI/CD resources such as pipelines, builds, jobs/logs, and build artifacts using a Buildkite API token configured in Zed.

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ Infrastructure mcp zed buildkite ci-cd integration editor-extension
⚙ Agent Friendliness
39
/ 100
Can an agent use this?
🔒 Security
44
/ 100
Is it safe for agents?
⚡ Reliability
20
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
35
Error Messages
0
Auth Simplicity
80
Rate Limits
10

🔒 Security

TLS Enforcement
60
Auth Strength
55
Scope Granularity
20
Dep. Hygiene
40
Secret Handling
40

Uses a Buildkite API token configured in Zed. The provided documentation does not specify least-privilege scopes, how tokens are stored, or whether token values could be logged. TLS and dependency hygiene cannot be verified from the supplied README/metadata alone.

⚡ Reliability

Uptime/SLA
0
Version Stability
30
Breaking Changes
30
Error Recovery
20
AF Security Reliability

Best When

You want Buildkite visibility and artifact/job-log exploration directly inside the Zed editor via MCP, and you’re comfortable granting the extension a Buildkite API token.

Avoid When

You require strict controls over where secrets are stored/logged, or you need formal guarantees about rate limiting, error codes, and pagination behavior being surfaced to the agent.

Use Cases

  • View recent Buildkite builds for a pipeline
  • Inspect jobs and retrieve job logs
  • List an organization’s pipelines
  • Download or review build artifacts from within Zed

Not For

  • Running or modifying Buildkite resources (e.g., triggering builds, creating/deleting pipelines) if not explicitly supported by the MCP tools
  • Organizations that cannot store/handle Buildkite API tokens in editor configuration

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: Buildkite API token (buildkite_api_token) configured in Zed settings
OAuth: No Scopes: No

The README indicates an API token is required and is configured in Zed. It does not describe token scope minimization or which Buildkite permissions are needed.

Pricing

Free tier: No
Requires CC: No

No pricing information is provided for the MCP extension or usage.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Only a high-level README is provided; specific MCP tool names, input/output schemas, pagination behavior, and error codes are not documented here.
  • Token-based auth is required; agents may inadvertently expose secrets if logs or prompts echo configuration values.
  • No guidance is provided for handling Buildkite API rate limits or transient failures within MCP calls.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for zed-mcp-server-buildkite.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered