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
uv tool install zadig-workflow-mcp
zadig-mcp init
zadig-mcp login
init lists all supported clients and marks the detected ones. Move with the up and down arrow keys, toggle each client with Space, and press Enter to confirm. Press Ctrl+C or confirm an empty 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.
The default company entry zadig provides testing, production, and combined releases. Existing clients get all three shortcuts the next time they start the upgraded server. Both company sites use the same saved LDAP credentials and maintain separate sessions.
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.
zadig-mcp init --agent cursor --name zadig-other --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.
Zadig Local signs in automatically with the current user's saved Zadig or Archery LDAP credentials when a session is missing or expires. If credentials are missing or LDAP rejects them, run zadig-mcp login in an interactive terminal. It prompts for your LDAP username and password and saves them after LDAP login succeeds.
Use --name on init to register a second instance alongside the default zadig entry. For a Dex LDAP site, use --auth ldap to store credentials for that site. Use --auth shared-ldap when you want the specified HTTPS site to use the same saved Zadig Local or Archery LDAP account. Sessions are stored per site. Supply the same --url and --auth to login.
Other stdio MCP clients can launch zadig-mcp without a subcommand and pass the same --url and --auth options.
Release through Zadig
Zadig checks out the selected branch from the remote repository configured in the workflow. Use the Zadig forms and workflow data to plan the release, and skip local Git branch, status, and diff checks.
Each new release request opens its own form. An earlier cancellation applies to that request only. If a form closes before submission, the tool reports the step and action. Follow a submitted release by the task ID returned for that request.
Use release_interactively in a client with MCP form support. When influxai / dev01 is available, the tool opens its branch and service form directly. Select 重新选择工作流 on that form to choose another project or workflow. Choose one or more services from the live workflow options. Influx preselects backend, frontend, and task when those targets are available. You can change the selection and edit the Git branch, which defaults to production. Review the complete release and approve it to submit. Use get_workflow_task to follow the returned task ID through build and deployment. run_workflow prefills the branch and services with the supplied values and goes through the same user confirmation. Both release tools require a client with MCP form support.
Influx release shortcuts
release_testopens the Influx dev01 branch and service form.release_productionpromotes the images from a successful dev01 task selected by the user. The review shows the destination, source task, each component's actual Git revision, the current production Helm tag, and the image to deploy. The tool verifies that the candidate tags are present in the production registry and rechecks the production tags and candidate records after approval. If the review data changes, it stops for a new confirmation.release_test_and_productionstarts a dev01 release and returns the test task ID. Call the same tool on the same MCP session with that ID to continue. It can return a waiting status. Once dev01 passes, the tool confirms and deploys the same set of service images. A failed or cancelled test ends the combined release.
Use the default zadig entry for all three shortcuts. For queries, specify site="production" or site="test" when needed. The test and production approvals are separate. Existing zadig-prod registrations remain supported. Use --influx-production when registering an alternate Influx production site explicitly.
Read task logs
get_workflow_task includes the error reported by Zadig for each step when available. Call get_workflow_task_log with the same project, workflow, and task ID, plus the stage type and step name returned by get_workflow_task.
For product workflow builds, the tool returns the last 100 lines of the archived build log by default. Set tail_lines to 1–500. Output is capped at 24,000 characters. For deployment steps, the tool returns the failure detail from the Zadig task record when available. A null log means that no log text is available for that step.
Metadata
Release files for zadig-workflow-mcp 0.1.16
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zadig_workflow_mcp-0.1.16-py3-none-any.whl | Python 3 | none | any | Details for zadig_workflow_mcp-0.1.16-py3-none-any.whl |
Release files / zadig_workflow_mcp-0.1.16-py3-none-any.whl
| Download URL | zadig_workflow_mcp-0.1.16-py3-none-any.whl |
|---|---|
| Size | 23.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7baf0b7320888b925bdd30d048013044a201c94fc9d645080a539f489de6dee5
|
|
BLAKE2b-256 checksum How to use checksums |
6da37cd33ff78ff3b5fec071f1502b7b164c77f8e86b4a489fb35f5de8d1ad8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.26 {"installer":{"name":"uv","version":"0.11.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for zadig-workflow-mcp 0.1.16
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.