Pipefy

Pipefy AI Toolkit

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 182 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	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 · [email protected]

---

Installation

Pre-1.0 ships pre-release builds to PyPI on every tag; uvx and uv tool install resolve them. A stable PyPI release becomes the default at v1.0. The current pre-release line is v0.3.0-beta.* (latest tag: v0.3.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 (or hosted MCP).

The CLI snippets below install pipefy-cli from PyPI, which resolves pipefy and pipefy-auth transitively (no explicit --with needed). While the toolkit ships only pre-release versions (the 0.x line), uv resolves the latest pre-release automatically; to pin a specific one, use pipefy-cli==X.Y.Z (PEP 440 form, e.g. pipefy-cli==0.3.0b1). Do not pass a global --prerelease allow: it also lets transitive dependencies jump to their own pre-releases, which can pull a broken build.

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

First-time / ask your agent: paste a setup request into Claude or Cursor and point them at this section — the checklist is skills/onboarding/pipefy-toolkit-setup/SKILL.md. Pick one MCP registration named pipefy (do not mix hosted HTTP and local stdio/plugin under the same name).

Hosted MCP (Claude Code)

Zero local Python: Claude Code connects over HTTPS. Auth is the client OAuth flow (--client-id pipefy-mcp). Hosted exposes the remote-safe tool surface only.

Do not run this if you already have a local/plugin MCP named pipefy (or another Pipefy stdio entry you intend to keep). Remove the conflicting registration first: claude mcp remove pipefy -s user (adjust name/scope), or use the Claude Code plugin path instead of hosted.