Pipefy

pipefy-labs

Open-source toolkit for Pipefy developers: a Model Context Protocol (MCP) server for AI agents, a pipefy CLI for terminals and automation, a shared GraphQL SDK, and a catalog of agent skill playbooks.

Overview • Installation • Repository layout • MCP server • CLI • Agent skills • Documentation • Development • Contributing

---

Overview

Component	Package / path	Purpose
MCP server	pipefy-mcp-server	Exposes 149 tools to MCP clients (Cursor, Claude Desktop, Claude Code, and others).
CLI	pipefy-cli	Terminal commands aligned with MCP capabilities; see docs/parity.md.
SDK	pipefy-sdk	Vendor GraphQL client, services, and models shared by MCP and CLI.
Skills	skills/	Markdown playbooks (Anthropic Skills format) for common Pipefy workflows.

Feedback and issues: GitHub Issues · dev@pipefy.com

---

Installation

Pre-1.0 ships from this git repo via uvx and uv tool install. PyPI becomes the canonical source at v1.0. The current beta line is v0.2.0-beta.* (first tag: v0.2.0-beta.1). Two install paths: the Quick install script below (resolves the latest GitHub Release at runtime and runs uv tool install for you), or Claude Code via the plugin marketplace.

The CLI snippets below pin @latest, a moving git tag the release flow updates to point at the most recent release. To pin a specific version, swap @latest for a version tag (e.g. @v0.2.0-beta.2). The --with pipefy-sdk @ ...#subdirectory=packages/sdk / pipefy-auth @ ...#subdirectory=packages/auth flags are required pre-1.0: this repo is a uv workspace, and the workspace members are not yet published to PyPI, so uv needs them named explicitly. The flags go away at v1.0 (PyPI install).

Two auth paths:

• Human OAuth (interactive): pipefy auth login runs the browser flow and stores a session in your OS keychain. Works anywhere the pipefy CLI is on PATH (uv tool install once, any client can invoke it). Claude Code additionally exposes it as the /pipefy:login slash command via the plugin marketplace. Pipe membership is whatever the signed-in user already has.
• Service account (unattended / CI): provision a Service Account in Pipefy Admin (Admin → Service Accounts) and add that account to every pipe the tools should touch. Wire PIPEFY_SERVICE_ACCOUNT_CLIENT_ID and PIPEFY_SERVICE_ACCOUNT_CLIENT_SECRET into the client config below.

Full env-var reference and config.toml precedence: docs/config.md.

Quick install (recommended)

One command installs the CLI + MCP server, optionally adds skills, and registers the MCP server in your client config:

curl -fsSL https://raw.githubusercontent.com/pipefy/ai-toolkit/main/install.sh \
  | sh -s -- --client cursor

Replace --client cursor with one of: claude-code, claude-desktop, codex, or none (prints the snippet to paste). Useful flags:

• --yes skip all confirmation prompts.
• --no-skills skip the npx skills add step.
• --version vX.Y.Z pin a specific GitHub Release tag (default: most recent prerelease or release).
• --dry-run print every command without executing.
• --allow-root opt-in for root execution (refused by default).

After install, run pipefy auth login to authenticate (--device on headless systems). The installer puts pipefy-mcp-server on PATH, so each client's config collapses to {"command": "pipefy-mcp-server"}.

Claude Code