Metadata-Version: 2.5
Name: zadig-workflow-mcp
Version: 0.1.1
Summary: A local MCP server for browsing, building and releasing Zadig product workflows
Keywords: ci-cd,deployment,mcp,zadig
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Topic :: Software Development :: Build Tools
Requires-Python: >=3.11
Requires-Dist: httpx==0.28.1
Requires-Dist: keyring<26,>=25
Requires-Dist: mcp==1.29.0
Requires-Dist: tomlkit<1,>=0.13
Description-Content-Type: text/markdown

# Zadig Workflow MCP

Zadig Workflow MCP is a local stdio server for finding product workflows, selecting build targets, running releases, and checking deployment status. The interactive release tool shows the project, workflow, environment, branch, and selected services before requesting confirmation.

## Install and connect an Agent

```sh
uv tool install zadig-workflow-mcp
zadig-mcp init
zadig-mcp login
```

`init` lists all supported clients and marks the detected ones. Enter the numbers of the clients you want to configure, or press Enter without a selection to cancel. For scripts and non-interactive shells, specify the clients explicitly, for example `zadig-mcp init --agent codex --agent cursor`. Choices are `codex`, `claude-code`, `claude-desktop`, `cursor`, `vscode`, `gemini`, and `opencode`.

To install a downloaded wheel, pass its path to `uv tool install`. `init` updates the selected clients' user configurations. `--replace` replaces a different MCP entry with the same name, and `--credentials-only` skips registration. A configuration file containing JSON comments or trailing commas can be edited manually if `init` reports that it cannot update the file.

Set up a different Zadig instance by supplying its HTTPS URL for both commands.

```sh
zadig-mcp init --agent cursor --url https://zadig.example.com --auth token
zadig-mcp login --url https://zadig.example.com --auth token
```

Enter your API token in the terminal prompt. Credentials are stored through the system keyring, and the MCP configuration contains the launch command and site options. The built-in Zadig Local profile can also reuse your existing local Archery MCP LDAP account. Each user retains their own Zadig permissions. Headless installations can set `ZADIG_API_TOKEN` in the MCP process environment.

Other stdio MCP clients can launch `zadig-mcp` without a subcommand and pass the same `--url` and `--auth` options.

## Release through Zadig

Use `release_interactively` in a client with MCP form support. Select the project and product workflow, enter a branch, and select services. Review the complete release and approve it to submit. Use `get_workflow_task` to follow the returned task ID through build and deployment. Clients without form support can collect and confirm the same parameters in chat before calling `run_workflow`.
