buildkite-mcp-server

Created By
wolfeidaua year ago
This is an mcp server for buildkite.
Overview

What is buildkite-mcp-server?

buildkite-mcp-server is a Model Context Protocol (MCP) server designed for Buildkite, providing access to information about pipelines, builds, and jobs to various tools and editors.

How to use buildkite-mcp-server?

To use the buildkite-mcp-server, you need to create a Buildkite API token with read access to pipelines, build the binary using make build, and configure it with the necessary API token.

Key features of buildkite-mcp-server?

  • Access to Buildkite pipeline details through the get_pipeline tool.
  • Ability to list all pipelines in a Buildkite organization using the list_pipelines tool.

Use cases of buildkite-mcp-server?

  1. Integrating Buildkite data with tools like Claude Desktop and GitHub Copilot.
  2. Automating the retrieval of pipeline information for CI/CD processes.

FAQ from buildkite-mcp-server?

  • Is buildkite-mcp-server ready for production use?

No, this project is in the early stages of development and is not yet ready for use.

  • What are the prerequisites for using buildkite-mcp-server?

You need to have Go 1.24 and Goreleaser installed to build the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
wolfeidau
Star
0
Language
Go
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago