Exposes an API-compatible replica of the Buildkite surface as part of the simulated olympus-labs data set, so agents can exercise Buildkite-shaped requests read-only without test accounts or cleanup.
Enables AI agents to read realistic, coherent data—repos, pull requests, issues, commits, users—through API-compatible, read-only replicas of 21 developer platforms including GitHub, Jira, Linear, Slack, Sentry and Salesforce, all preloaded with one simulated company so integrations can be built and tested with no accounts, credentials, rate-limit worry, or cleanup.
10
266 npm
MIT
Why this server?
Enables triggering XenoCI remote macOS builds from Buildkite CI using the XenoCast CLI and an API key secret.
Routes MCP requests intelligently to multiple backend servers through a single gateway, bypassing tool limits by exposing only 2 routing tools while providing access to unlimited backend tools across services like GitHub, databases, and more.
MIT
Why this server?
Integrates with Buildkite CI/CD platform through environment variable token configuration
Gateway MCP Server - Route MCP requests intelligently to multiple backend servers.
3
MIT
Why this server?
Exposes Buildkite data including pipelines, builds, jobs, and test results, allowing AI tools to interact with Buildkite CI/CD infrastructure. Provides tools for managing clusters, queues, pipelines, builds, artifacts, annotations, and test executions.
AI-native, zero-config CI/CD. Detects 33 languages + 40 frameworks, generates pipelines, runs locally at $0 cloud cost, diagnoses failures with AI, and deploys to 20 targets.
-
Why this server?
Retrieve information from Buildkite, including organizations, pipelines, builds, jobs, and job logs, and perform actions like retrying jobs and listing failures.
