MCP server for Pipefy
About
MCP server, CLI, and agent skills for Pipefy.
Details
- Author
- gbrlcustodio
- GitHub stars
- 34
- Downloads
- 193
- Categories
- Other
Jump to
- 152 tools across ten domains (pipes & cards, databases, reports, automations, etc.)
- Supports both human OAuth and service account authentication
- Part of a larger open-source toolkit (CLI, SDK, agent skill playbooks)
- Compatible with any MCP client (Cursor, Claude Desktop, Claude Code, Codex)
- Ships with a skill catalog of workflow playbooks for common Pipefy tasks
- Open source under Apache 2.0 license
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
MCP server for PipefyCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install via the recommended quick install script (curl -fsSL ... | sh) or through the Claude Code plugin marketplace. After installation, authenticate using either human OAuth (pipefy auth login) or a service account (set PIPEFY_SERVICE_ACCOUNT_CLIENT_ID and PIPEFY_SERVICE_ACCOUNT_CLIENT_SECRET). Configure your MCP client to run the pipefy-mcp-server command. The server is used by connecting any MCP-compatible client to the running server process.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mcp server for pipefy": {
"pipefy-mcp-server": {
"command": "uv",
"args": [
"tool",
"install",
"\\"
]
}
}
}
}McpServers
{
"pipefy-mcp-server": {
"command": "uv",
"args": [
"tool",
"install",
"\\"
]
}
}MCP server
The server registers 152 tools across ten domains. Canonical names: PIPEFY_TOOL_NAMES in packages/mcp/src/pipefy_mcp/tools/registry.py.
Tool descriptions and Args: blocks come from Python docstrings (what MCP clients show to models). Per-area reference docs cover parameters, edge cases, and cross-cutting behavior.
Shared conventions (pagination, IDs, permissions, error shape): docs/mcp/tools/cross-cutting.md.
| Domain | Tools | Summary | Reference |
|--------|:-----:|---------|-----------|
| Pipes & cards | 40 | Pipes, phases, fields, labels, cards, field conditions, attachments. Phase inventory (get_phase_cards, get_phase_cards_count), move discovery (get_phase_allowed_move_targets), and create_card(phase_id=…) reduce raw GraphQL for agent seeding. | docs |
| Database tables | 17 | Tables, records, schema, table-record attachments. | docs |
| Relations | 8 | Pipe and card relations. | docs |
| Reports | 17 | Pipe and organization reports, async exports. | docs |
| Automations & AI | 23 | Automations, AI automations, AI agents, validators. | docs |
| Observability | 10 | Logs, usage, credits, job exports. | docs |
| Members, email & webhooks | 11 | Membership, inbox email, webhooks. | docs |
| Organization | 1 | Organization metadata. | docs |
| Portals | 20 | Portal read/CRUD, pages, elements, sub-portals (publish/unpublish). | docs |
| Introspection | 5 | Schema discovery and raw GraphQL. | docs |
---
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
