@jurislm/woodpecker-ci-plugin 2.0.1 → 2.0.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "woodpecker-ci",
3
- "version": "2.0.1",
3
+ "version": "2.0.3",
4
4
  "description": "Manage Woodpecker CI through agent tools.",
5
5
  "author": {
6
6
  "name": "JurisLM",
package/README.md CHANGED
@@ -1,6 +1,7 @@
1
1
  # @jurislm/woodpecker-ci-plugin
2
2
 
3
- Local stdio MCP server for Woodpecker CI.
3
+ One Woodpecker CI guidance skill backed by a local stdio MCP server. The skill
4
+ guides safe tool selection; the server exposes the Woodpecker API.
4
5
 
5
6
  ## Requirements
6
7
 
@@ -35,9 +36,9 @@ The server does not read `DRONE_TOKEN`.
35
36
  ```
36
37
 
37
38
  The server exposes generated OpenAPI operations plus a focused pipeline
38
- inspection tool. Personal-token lifecycle and pprof operations are excluded.
39
- The `/version` operation is also excluded because the configured Woodpecker
40
- instance returns its HTML app shell for that path instead of JSON.
39
+ inspection tool. It excludes `/user/token`, `/version`, and `/debug/pprof` plus
40
+ its subpaths. The OpenAPI snapshot describes `/version` as JSON, but this
41
+ configured instance serves its HTML app shell at `/api/version`.
41
42
  It is a local stdio package, not a hosted ChatGPT plugin endpoint.
42
43
 
43
44
  Generated tool names, titles, descriptions, input schemas, output schemas, and
@@ -58,6 +59,7 @@ This repository also contains the portable Agent Plugin layer:
58
59
  - `mcp.json` — stdio MCP server configuration.
59
60
  - `.codex-plugin/plugin.json` — Codex compatibility fallback.
60
61
  - `.agents/plugins/marketplace.json` — repository-root Codex marketplace entry.
62
+ - `.cursor-plugin/` — Cursor marketplace, plugin metadata, and MCP variables.
61
63
  - `.mcp.json.example` — local configuration example without secrets.
62
64
  - `skills/woodpecker-ci/SKILL.md` — service-specific tool-selection guidance.
63
65
  - `.mcp.json` — Codex MCP registration, matching the portable `mcp.json`.
@@ -77,10 +79,36 @@ codex plugin add woodpecker-ci@woodpecker-ci-marketplace
77
79
 
78
80
  The server can initialize and list its tools before credentials are set.
79
81
  Provider calls require `WOODPECKER_URL` and `WOODPECKER_API_TOKEN` in the MCP
80
- server process environment. A GUI-launched Codex app may not inherit shell
81
- profile variables, so do not rely on `~/.zshenv` alone. Keep token values out
82
- of repository files. Open a new task after installing or updating the plugin
83
- so Codex loads its current tool catalog.
82
+ server process environment. A desktop app launched by macOS does not read your
83
+ interactive shell configuration. Check the MCP child process, not the terminal,
84
+ when diagnosing missing credentials.
85
+
86
+ If an existing `~/.zshenv` exports the token, this local Codex configuration
87
+ launches the MCP server through zsh without copying the token into Codex config
88
+ or this repository. Replace the example URL with your Woodpecker API URL:
89
+
90
+ ```toml
91
+ [mcp_servers.woodpecker-ci]
92
+ command = "/bin/zsh"
93
+ args = ["-c", "exec /usr/bin/python3 -c 'import os; keys=(\"HOME\",\"PATH\",\"TMPDIR\",\"WOODPECKER_API_TOKEN\"); env={k:os.environ[k] for k in keys if k in os.environ}; env[\"WOODPECKER_URL\"]=\"https://ci.example.com/api\"; path=env[\"HOME\"]+\"/.bun/bin/bunx\"; os.execve(path,[path,\"-y\",\"@jurislm/woodpecker-ci-plugin@latest\"],env)'"]
94
+ required = true
95
+ startup_timeout_sec = 30
96
+ ```
97
+
98
+ This example needs `/usr/bin/python3` and Bun at `$HOME/.bun/bin/bunx`; replace either absolute path if needed. Python passes the token through `execve` environment, never a command argument.
99
+
100
+ `required = true` waits for this MCP server during tool discovery. Check
101
+ `codex mcp get woodpecker-ci`, then open a new Codex task and confirm that its
102
+ Woodpecker tools are present and an authenticated read succeeds. A successful
103
+ local stdio check alone does not verify the task's tool catalog. Keep token
104
+ values out of repository files and diagnostic output.
105
+
106
+ ## Cursor installation
107
+
108
+ In Cursor, open Customize → Add Marketplace → Import from GitHub and enter
109
+ `https://github.com/jurislm/woodpecker-ci-plugin`. Add Woodpecker CI Plugin,
110
+ then use Configure to set `WOODPECKER_URL` and `WOODPECKER_API_TOKEN`. Cursor
111
+ stores the values outside this repository.
84
112
 
85
113
  ## Development
86
114
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jurislm/woodpecker-ci-plugin",
3
- "version": "2.0.1",
3
+ "version": "2.0.3",
4
4
  "description": "Local stdio MCP server for Woodpecker CI",
5
5
  "type": "module",
6
6
  "bin": {
package/plugin.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
3
3
  "name": "woodpecker-ci",
4
- "version": "2.0.1",
4
+ "version": "2.0.3",
5
5
  "description": "Manage Woodpecker CI through agent tools.",
6
6
  "author": {
7
7
  "name": "JurisLM",
@@ -11,4 +11,15 @@ Use the Woodpecker MCP tools for live CI state and actions.
11
11
  - Use read-only tools before write tools.
12
12
  - Treat pipeline cancellation, deletion, token reset, secret changes, and repository changes as consequential.
13
13
  - Never expose WOODPECKER_API_TOKEN or credential fields from tool results in narration.
14
+ - Pass tokens to local MCP processes through environment variables; never expand a token into command arguments.
14
15
  - Report source, pipeline number, commit SHA, status, and API error status separately.
16
+
17
+ ## Availability check
18
+
19
+ When asked whether the installed plugin works, record three separate results:
20
+
21
+ 1. `codex mcp get woodpecker-ci` confirms the effective server command; published stdio `initialize` and `tools/list` confirm package startup and tool count.
22
+ 2. The current Codex task must expose Woodpecker MCP methods. An empty task tool catalog is a registration failure even when the server is ready.
23
+ 3. A registered read-only `woodpecker_get_currently_authenticated_user` call confirms provider access. Status 0 with a missing configuration name identifies the MCP child environment; HTTP 200 confirms that read only.
24
+
25
+ Read the MCP child environment when diagnosing credentials. Shell variables, an installed plugin, and a direct local MCP call do not establish current-task access. Report the package version, tool count, API status, and task registration separately.