Skip to main content

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.

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 --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

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. Select the project and product workflow, then 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.

Metadata

Release files for zadig-workflow-mcp 0.1.8

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for zadig-workflow-mcp 0.1.8
File Interpreter ABI Platform Actions
zadig_workflow_mcp-0.1.8-py3-none-any.whl Python 3 none any Details for zadig_workflow_mcp-0.1.8-py3-none-any.whl

Release files / zadig_workflow_mcp-0.1.8-py3-none-any.whl

Download URL zadig_workflow_mcp-0.1.8-py3-none-any.whl
Size 15.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
32316df951d075bbf40db6c662709a1b16552dd51c343dd0573b010b725c3bce
BLAKE2b-256 checksum
How to use checksums
4cc0f509850f9bd3ed457ba7d10144788ff089cc62329c6fde436ef8d0af1445
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.8

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page