Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

pipefy-cli

Typer-based CLI for Pipefy. Exposes all MCP tool capabilities as terminal commands and scripts. Depends on pipefy for GraphQL calls.

Install

uvx --from pipefy-cli pipefy --help

Or persistently:

uv tool install pipefy-cli

pipefy-cli and its dependencies (pipefy, pipefy-auth) are published to PyPI, so uv resolves the whole set from there. While the toolkit ships only pre-release versions (the 0.x line), uv resolves the latest pre-release automatically; once a stable release exists it resolves that instead. Do not pass a global --prerelease allow: it also lets transitive dependencies jump to their own pre-releases, which can pull a broken build. The console script is pipefy, so uvx --from pipefy-cli runs it as pipefy.

Quick start

# Show all commands
pipefy --help

# Card operations
pipefy card get 12345 --json
pipefy card list --pipe 67890
pipefy card create --pipe 67890 --title "New card"

Agent skills are installed separately via skills.sh; see plugins/pipefy/README.md.

Configuration

Same PIPEFY_* environment variables as pipefy-mcp-server (.env in CWD is loaded automatically):

PIPEFY_SERVICE_ACCOUNT_CLIENT_ID=your_client_id
PIPEFY_SERVICE_ACCOUNT_CLIENT_SECRET=your_client_secret
# Non-prod environments only:
# PIPEFY_BASE_URL=https://<your-api-host>
# PIPEFY_AUTH_URL=https://<your-signin-host>/realms/<realm>

PIPEFY_BASE_URL defaults to https://app.pipefy.com (drives the four API endpoints) and PIPEFY_AUTH_URL defaults to https://signin.pipefy.com/realms/pipefy (the OIDC issuer). Set them only for non-prod environments.

Authentication paths

Three credential sources, in CLI precedence order:

  1. Interactive (pipefy auth login) — browser OAuth flow, session stored in the OS keychain. Best for human developers. Status and revocation via pipefy auth status and pipefy auth logout.
  2. Static bearer (PIPEFY_TOKEN or --token) — direct bearer token, no OAuth. Intended for CI and scripted use. Overrides everything else.
  3. Service-account OAuth (PIPEFY_SERVICE_ACCOUNT_CLIENT_ID + PIPEFY_SERVICE_ACCOUNT_CLIENT_SECRET) — unattended OAuth client-credentials grant. Used by the MCP server.

Full env-var reference, validation rules, and config.toml precedence: docs/config.md. Auth deep-dive (precedence rules, troubleshooting, keychain backends): docs/cli/auth.md.

Output modes

Every command defaults to Rich-formatted human output. Add --json for machine-readable JSON to stdout.

pipefy card get 12345 --json | jq '.title'

Parity with MCP

Every MCP tool has a CLI counterpart (or a tracked deferral). See docs/parity.md for the full matrix.

Shell completion

pipefy --install-completion bash    # or zsh, fish, etc.

Development

From the repository root:

uv sync
uv run pytest packages/cli/tests     # CLI tests
uv run ruff check packages/cli/src   # lint

See AGENTS.md for contributor guidance.

Metadata

Release files for pipefy-cli 0.5.8b1

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 pipefy-cli 0.5.8b1
File Interpreter ABI Platform Actions
pipefy_cli-0.5.8b1-py3-none-any.whl Python 3 none any Details for pipefy_cli-0.5.8b1-py3-none-any.whl

Release files / pipefy_cli-0.5.8b1-py3-none-any.whl

Download URL pipefy_cli-0.5.8b1-py3-none-any.whl
Size 95.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
65e606039242e534934b170378ebfd800445afb5d794d44c2dff587135663383
BLAKE2b-256 checksum
How to use checksums
0cd351910ab6624feca7afd565cd136aa91f16dc3e86b0cc9021440f41461a0b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

Security for pipefy-cli 0.5.8b1

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.

Full provenance

1 file in this release has been uploaded with provenance metadata.

Attestation for pipefy_cli-0.5.8b1-py3-none-any.whl

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

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