MCP server that exposes Pipefy's GraphQL API.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"pipefy-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# pipefy-mcp-server MCP server for Pipefy — **197 tools** for AI agents (Cursor, Claude Desktop, Claude Code, Codex, and any MCP-compatible client). Depends on [`pipefy`](../sdk/README.md) for all GraphQL and API logic. ## Install ```sh uvx pipefy-mcp-server ``` `pipefy-mcp-server` and its workspace dependencies (`pipefy`, `pipefy-auth`, `pipefy-infra`) are published to PyPI, so `uvx` resolves the whole set from there. While the toolkit ships only pre-release versions (the 0.x line), `uvx` 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. For per-client wiring (Claude Code / Cursor / Claude Desktop / Codex), see [`docs/install.md`](../../docs/install.md). ## Uninstall `./uninstall.sh --scan` (repository root) reports every Pipefy MCP registration on the machine, matched on what each one runs rather than on its name, plus the tools, credentials, skills, and plugin state behind them. A bare run removes what you approve, in tiers. Teardown reference and the hosted / local / plugin switching recipes: [`docs/uninstall.md`](../../docs/uninstall.md). ## Configuration Set the following environment variables (or add them to a `.env` file in the working directory, or pin them in `~/.config/pipefy/config.toml`): ```env 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. Full reference (every `PIPEFY_*` variable, validation rules, TOML schema, precedence chain): [`docs/c…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.