An MCP server for interacting with a Drone CI/CD instance. It can list and manage repositories, builds, cron jobs, secrets, users, and templates, and exposes build details as MCP resources.
From the registry: MCP server for Drone CI/CD with 47 tools for build, repo, secret, user, template and cron management
$ go build -o drone-mcp-server .Please install the `drone-mcp-server` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Set up a Drone personal access token** — Create a Drone token with permissions to read repositories and builds; additional permissions may be needed for write/admin operations exposed by the server.
Optional prerequisites:
- Install or obtain the Drone MCP Server binary — Build the server from source with Go, pull the Docker image, or download a pre-built binary from GitHub Releases. For the canonical config, use the compiled binary path. Run: `go build -o drone-mcp-server .` (https://github.com/yusiwen/drone-mcp-server/releases/)
Canonical MCP server config (stdio transport):
- command: `<path-to-drone-mcp-server>`
- args: []
- required environment variables:
- `DRONE_SERVER`: Base URL of your Drone instance. (example: `<your-drone-server-url>`)
- `DRONE_TOKEN`: Drone personal access token used to authenticate to the Drone API. (example: `<your-drone-token>`)
- optional environment variables:
- `MCP_AUTH_TOKEN`: Bearer token required only when running the server in SSE mode and you want clients to authenticate to the SSE endpoint. (example: `<your-sse-auth-token>`)
Note: Default transport is stdio. The server also supports SSE mode by running the binary with args ["--sse", "--host", "<host>", "--port", "<port>"] and, optionally, setting MCP_AUTH_TOKEN. For SSE clients, requests must include Authorization: Bearer <token> when MCP_AUTH_TOKEN is set.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.DRONE_SERVERrequiredBase URL of the Drone server instance.DRONE_TOKENrequiredPersonal access token used to authenticate to Drone and read repositories/builds.Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
Validate oh-my-posh configurations and segment snippets against the official schema.