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
454 npm
MIT
Why this server?
Lets the deploy command report deployments to MoleSignal, taking the commit, repository, pull request, author and run link from Buildkite.
Serves MoleSignal's tools over stdio to AI agent tools such as Claude Code, Cursor, Codex, VS Code, or Gemini CLI, enabling them to query logs, metrics, traces, incidents, approvals, deployments, and other capabilities under the user's permissions and organization policy.
446 npm
Apache 2.0
Why this server?
Enables triggering XenoCI remote macOS builds from Buildkite CI using the XenoCast CLI and an API key secret.
Enables AI agents to check the live operational status of hundreds of cloud, SaaS and AI providers, returning current state, affected components and active incidents for a named stack so agents can tell a vendor outage apart from their own broken code. It answers from a continuously polled local database, so agents can query stacks, list degraded providers, and review incident history without calling vendor status pages.
143 npm
MIT
Why this server?
Retrieve information from Buildkite, including organizations, pipelines, builds, jobs, and job logs, and perform actions like retrying jobs and listing failures.
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.
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.
