Can I use Buildkite as a CLI?

Yes. KosmoKrator exposes a Buildkite CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Buildkite through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Buildkite tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Buildkite credentials stored?

Buildkite credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Buildkite MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Buildkite MCP Gateway for AI Agents

Expose Buildkite tools to Claude Code, Cursor, Codex, and other MCP clients through the local KosmoKrator MCP gateway.

Buildkite MCP Gateway

Expose Buildkite to MCP clients with `kosmokrator mcp:serve --integration=buildkite`.

If the client has never used KosmoKrator before, install it first, then register this integration as a stdio MCP server.

Install KosmoKrator

curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

Install gateway entry

kosmokrator mcp:gateway:install --integration=buildkite --write=deny --json

MCP configuration

{
  "mcpServers": {
    "kosmokrator-buildkite": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=buildkite",
        "--write=deny"
      ]
    }
  }
}

Serve manually

kosmokrator mcp:serve --integration=buildkite --write=deny

Client Notes

Use one scoped MCP gateway entry, then adapt the config location to the client or framework.

Claude Code Connect local KosmoKrator integrations to Claude Code through one scoped MCP gateway entry. Claude Code can launch the local kosmo binary directly from the project MCP config.

Cursor Expose selected local integrations to Cursor through KosmoKrator without configuring each service as its own MCP server. Use the same KosmoKrator install and integration credentials that power terminal and headless runs.

Codex Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy. Keep write access denied or ask-based unless the workspace is trusted.

OpenAI Agents SDK Attach KosmoKrator integration tools to OpenAI Agents SDK workflows through a local MCP gateway. Use headless JSON commands for CI-style execution and MCP for agent tool discovery.

Claude Agent SDK Give Claude Agent SDK workflows access to KosmoKrator integrations through a local MCP server. Use a narrow integration list so the agent does not load unrelated tools.

Vercel AI SDK Use KosmoKrator as a local integration gateway for Vercel AI SDK agents and scripts. Prefer CLI JSON calls when a workflow only needs one deterministic integration operation.

LangChain Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls. Keep the gateway scoped to the integration and operation class needed by the chain.

LangGraph Run KosmoKrator integration calls from LangGraph nodes while preserving local credentials and permissions. Headless CLI calls fit repeatable graph edges; MCP fits exploratory agent nodes.

CrewAI Expose KosmoKrator integrations to CrewAI workers as scoped local tools. Use per-worker integration scopes to avoid giving every worker every tool.

Generic MCP Clients Connect any stdio-compatible MCP client to local KosmoKrator integration tools. Start with read-only write policy and expand only for trusted projects.

MCP Tool Names

KosmoKrator exposes integration tools through the gateway with stable names.

MCP tool	Source function	Type
`integration__buildkite__buildkite_get_current_user`	`buildkite.buildkite_get_current_user`	Read `read`
`integration__buildkite__buildkite_list_organizations`	`buildkite.buildkite_list_organizations`	Read `read`
`integration__buildkite__buildkite_get_organization`	`buildkite.buildkite_get_organization`	Read `read`
`integration__buildkite__buildkite_list_pipelines`	`buildkite.buildkite_list_pipelines`	Read `read`
`integration__buildkite__buildkite_get_pipeline`	`buildkite.buildkite_get_pipeline`	Read `read`
`integration__buildkite__buildkite_create_pipeline`	`buildkite.buildkite_create_pipeline`	Write `write`
`integration__buildkite__buildkite_update_pipeline`	`buildkite.buildkite_update_pipeline`	Write `write`
`integration__buildkite__buildkite_archive_pipeline`	`buildkite.buildkite_archive_pipeline`	Write `write`
`integration__buildkite__buildkite_unarchive_pipeline`	`buildkite.buildkite_unarchive_pipeline`	Write `write`
`integration__buildkite__buildkite_list_builds`	`buildkite.buildkite_list_builds`	Read `read`
`integration__buildkite__buildkite_get_build`	`buildkite.buildkite_get_build`	Read `read`
`integration__buildkite__buildkite_create_build`	`buildkite.buildkite_create_build`	Write `write`
`integration__buildkite__buildkite_cancel_build`	`buildkite.buildkite_cancel_build`	Write `write`
`integration__buildkite__buildkite_rebuild_build`	`buildkite.buildkite_rebuild_build`	Write `write`
`integration__buildkite__buildkite_retry_failed_jobs`	`buildkite.buildkite_retry_failed_jobs`	Write `write`
`integration__buildkite__buildkite_get_job_log`	`buildkite.buildkite_get_job_log`	Read `read`
`integration__buildkite__buildkite_get_job_environment`	`buildkite.buildkite_get_job_environment`	Read `read`
`integration__buildkite__buildkite_api_get`	`buildkite.buildkite_api_get`	Read `read`
`integration__buildkite__buildkite_api_post`	`buildkite.buildkite_api_post`	Write `write`
`integration__buildkite__buildkite_api_put`	`buildkite.buildkite_api_put`	Write `write`
`integration__buildkite__buildkite_api_patch`	`buildkite.buildkite_api_patch`	Write `write`
`integration__buildkite__buildkite_api_delete`	`buildkite.buildkite_api_delete`	Write `write`

Write Access

Start with --write=deny for read-only MCP clients. Use --write=ask or --write=allow only when the client and workspace are trusted.