Schema | woodpecker-mcp

woodpecker-mcp

Describes the environment variables required to run the server.

Name	Required	Description
`WOODPECKER_URL`	No	URL of a Woodpecker CI instance (single instance configuration).
`WOODPECKER_TOKEN`	No	Personal access token for the Woodpecker instance (required).
`WOODPECKER_SERVER`	No	Alternative environment variable for the Woodpecker instance URL (official CLI variable).

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
list_instancesA	Lists the configured Woodpecker CI instances. Use `check: true` to verify each instance is reachable and the token is valid.
list_reposA	Lists repositories the token has access to on a Woodpecker instance. Returns repo ids usable with the other tools.
list_pipelinesA	Lists recent pipelines for a repository, newest first. Filter by branch, event or status to find e.g. the CI runs for a pull request branch.
get_pipelineA	Gets one pipeline with its workflows and steps (names, states, exit codes). Failed step ids are listed in `failed_step_ids` — fetch their output with get_step_logs.
get_step_logsA	Fetches the log output of one pipeline step (use the step ids from get_pipeline). Returns the last `tail` lines.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RikiGomes/woodpecker-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server