Drone CI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRONE_TOKEN | Yes | Drone API token | |
| DRONE_BASE_URL | Yes | Drone base URL (for example https://drone.example.com) | |
| DRONE_TIMEOUT_MS | No | Drone connection timeout in milliseconds | 10000 |
| DRONE_MAX_RETRIES | No | Maximum number of retries for Drone API requests | 2 |
| DRONE_WEBHOOK_SECRET | Yes | shared secret to verify webhook signatures | |
| MCP_ENABLE_WRITE_ACTIONS | No | Whether to enable write actions (keep disabled until authorization guardrails are in place) | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| drone_pingA | Minimal diagnostic tool for MCP client compatibility checks. |
| drone_list_reposC | List repositories visible to the Drone token. |
| drone_list_buildsC | List builds for a repository. |
| drone_get_buildC | Get one build details by build number. |
| drone_get_build_logsC | Get logs for one build stage/step. |
| drone_get_cached_build_stateB | Read webhook-cached build state. If buildNumber is omitted, returns recent snapshots for the repository. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct purpose: build details, logs, cached state, listing builds, listing repos, and a ping diagnostic. No overlapping functionality.
All tools follow a consistent drone_<verb>_<noun> pattern, making them predictable and easy to navigate.
Six tools is well-scoped for a CI integration, covering core retrieval operations without unnecessary bloat.
The set focuses on read-only operations (get, list, ping) but lacks build creation, cancellation, or update actions, which are common for CI workflows.