MCP server, CLI, and agent skills for Pipefy.
For Pipefy MCP server exists for a simple reason — assistants are far more useful when they can act on For Pipefy directly instead of describing what you should do. MCP server, CLI, and agent skills for Pipefy.
Overview • Installation • Repository layout • MCP server • CLI • Agent skills • Documentation • Development • Contributing • Legal
Feedback and issues: GitHub Issues · dev@pipefy.com
Once For Pipefy is connected, these are the calls the assistant has available:
Component — Package / pathCLI — pipefy-cliSDK — pipefySkills — skills/Path — DistributionDomain — ToolsRelations — 8Reports — 17iPaaS — 4Observability — 11Organization — 2Portals — 20You will need 3 environment variables: PIPEFY_SERVICE_ACCOUNT_CLIENT_ID, PIPEFY_SERVICE_ACCOUNT_CLIENT_SECRET, PIPEFY_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. For Pipefy's toolset — Component, CLI, SDK and 11 more — is a fair guide to whether it matches your workflow. It is maintained by gbrlcustodio; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Component | Package / path |
| CLI | pipefy-cli |
| SDK | pipefy |
| Skills | [skills/](skills/) |
| Path | Distribution |
| Domain | Tools |
| Relations | 8 |
| Reports | 17 |
| iPaaS | 4 |
| Observability | 11 |
| Organization | 2 |
| Portals | 20 |
| Introspection | 5 |
| Control | Set with |
{
"mcpServers": {
"pipefy": {
"command": "npx",
"args": ["-y", "skills"],
"env": {
"PIPEFY_SERVICE_ACCOUNT_CLIENT_ID": "your-value",
"PIPEFY_SERVICE_ACCOUNT_CLIENT_SECRET": "your-value",
"PIPEFY_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| PIPEFY_SERVICE_ACCOUNT_CLIENT_ID | Configuration value read at startup. | Optional |
| PIPEFY_SERVICE_ACCOUNT_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| PIPEFY_TOKEN | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.