Buildkite (API Token) MCP server
Official Buildkite remote MCP authenticated with a Buildkite API access token instead of OAuth. Connect your AI agents to Buildkite (API Token) with enterprise-grade governance, observability, and control through MintMCP Gateway.
Works with every major client
Why MintMCP gateway
Centralized governance
Unified authentication, audit logging, and rate control for all Buildkite (API Token) MCP connections.
One-click deployment
Instantly enable Buildkite (API Token) MCP for AI teams via MintMCP's standardized gateway without manual server setup.
OAuth + SSO enforcement
Automatic enterprise authentication wrapping for Buildkite (API Token) MCP endpoints.
Host stdio servers on MintMCP instead of running locally
Containerized servers become accessible to clients like ChatGPT without local installations. Better risk management and security posture without requiring users to run servers on their machines.
Observability and control
Real-time dashboards for monitoring usage, detecting anomalies, and maintaining SLA compliance.
Enterprise hardening
High availability, security, and compliance alignment transform MCP from developer utility to production-grade infrastructure.
Supports shared and per-user auth
Flexibility to configure service accounts at the admin level or enable individual OAuth flows. Secrets remain protected while users gain access, with centralized revocation capabilities.
Granular tool access control
Configure tool access by role. For example, enable read-only operations and exclude write tools like create and delete.
FAQs
Yes. MintMCP Gateway is SOC 2 compliant and uses OAuth-based authentication for all Buildkite (API Token) MCP interactions.