4,000+ servers built on MCP Fusion
Vinkius

Integrate Pipefy with Claude, Cursor, Chatbots & AI Agents MCP Server

Manage workflows via Pipefy — list pipes, create cards, move phases, update fields, and track processes directly from any AI agent.
MCP Inspector GDPR Free for Subscribers

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
clone

Clone card on Pipefy

You must provide the card_id of the card to clone. The new card is created in the same pipe as the original, starting at the first phase. This is useful for creating similar requests, repeating processes, or using an existing card as a template for new items. The cloned card gets a new unique ID but retains all field data. Clone an existing card to create a duplicate

create

Create card on Pipefy

You must provide the pipe_id and a JSON object containing field values matching the pipe's required fields. Fields are key-value pairs where keys are field IDs and values are the data to store. Optionally specify a phase_id to start the card in a specific phase (defaults to first phase). Example fields: { "name": "John Doe", "email": "john@example.com", "priority": "High" } Create a new card in a Pipefy pipe

delete

Delete card on Pipefy

You must provide the card_id. This action cannot be undone. Use this to remove test cards, duplicates, or items that were created in error. Be careful as this will also remove all associated data including comments, attachments, and field values for that card. Delete a card from a pipe

get

Get card on Pipefy

Use the card_id obtained from list_cards to inspect full card information. This is useful for reviewing card details before updating fields or moving to another phase. Get detailed information about a specific card

get

Get organization on Pipefy

Use the organization_id to inspect your organization's structure, understand team membership, and discover available pipes for card management. Get details of a Pipefy organization

get

Get phase on Pipefy

Phases represent steps in a pipe's workflow. Use the phase_id obtained from get_pipe or list_phases to inspect phase configuration. This helps understand what fields are required at each step of the workflow. Get details of a specific phase

get

Get pipe on Pipefy

Each pipe represents a workflow or process with multiple phases (steps) and custom fields. Use the pipe_id to get the structure of a pipe before creating cards or managing cards within it. The response includes all phases with their IDs, names, and the custom fields defined for the pipe. Get details of a specific Pipefy pipe (process)

get

Get user profile on Pipefy

Use this to verify API token access and discover organization IDs needed for other queries. This is also useful for understanding which organizations and pipes the user has access to. Get the authenticated user profile

list

List cards on Pipefy

Cards represent individual items flowing through the pipe's workflow phases (e.g., requests, tasks, tickets, leads). You must provide the pipe_id. Optionally filter by phase_id to see cards in a specific phase. Each card includes title, current phase, completion status, due date, and assignees. Use this to monitor workflow progress and identify cards that need attention. List all cards in a pipe with optional phase filter

list

List phases on Pipefy

Each phase represents a stage that cards flow through in the process. Use this to understand the workflow structure and identify phase IDs for filtering cards or moving cards between phases. The response includes phase names and card counts. List all phases in a pipe

list

List pipes on Pipefy

Each pipe represents a structured workflow with phases, fields, and cards. You must provide the organization_id which can be found in your Pipefy URL or obtained from get_user_profile. Use this to discover all available pipes before managing cards within them. List all pipes in an organization

move

Move card to phase on Pipefy

You must provide the card_id and the target phase_id. This is the primary way to advance workflow items through the pipe's process steps. Common use cases: moving a request from "New" to "In Review", advancing a lead to "Qualified", or progressing a task to "Completed". The card retains all its field values after moving. Move a card to a different phase in the pipe

search

Search cards by field on Pipefy

This is useful for finding cards by email, name, ID, or any custom field content. You must provide the pipe_id, field_id (the field to search in), and search_value (text to find). Results include card title, current phase, status, and all field values for matching cards. The search uses a "contains" operator for flexible matching. Search cards in a pipe by a specific field value

update

Update card field on Pipefy

You must provide the card_id, the field_id of the field to update, and the new value as a string. This is useful for updating card information as requests progress or details change. Common updates: changing priority, updating contact info, modifying descriptions, or setting dates. Update a specific field value on a card

Security & Code Integrity Audit

Every tool in the Pipefy MCP Server is continuously audited by the Vinkius Security Engine. We guarantee zero-trust payload isolation, strict data boundaries, and deterministic execution for enterprise-grade AI agents.

MCP Inspector
A+Score: 100

How Vinkius protects your data

Is there a risk of the AI "going crazy" and deleting important company data?

No. With Vinkius, the AI operates on "rails". It can only make the exact moves you authorized in the tool's settings. It cannot invent routes, access other networks in your company, or decide to delete random files. If the action isn't in the approved catalog, the attempt is blocked instantly.

Can I audit what my AI agents are doing with this integration?

Yes, Vinkius provides an immutable, HMAC-chained audit log. Every tool execution, payload, and response is tracked in real-time on your dashboard, giving you complete visibility into your agent's actions.

Can I search for cards by a specific field value like email or customer name?

Yes! Use the search_cards_by_field tool with the pipe_id, field_id (the specific field to search in), and search_value (the text to find). This searches all cards in the pipe where that field contains your search text. It's perfect for finding cards by customer email, name, order number, or any custom field. Results include full card details with all field values.

What if the AI ends up reading customer data or confidential information?

We have a built-in digital "bodyguard" called DLP (Data Loss Prevention). If a tool fetches data and the response contains social security numbers, credit cards, or personal customer info, Vinkius magically blocks and erases that information before it is delivered to the AI. The AI works only with what is strictly necessary, and your sensitive data never leaks.

Automated Workflows using Pipefy

Add the Pipefy tool to your AI Agents. The toolkit allows Claude and ChatGPT to securely fetch and update targeted data.

Connecting process management with Cursor

Use the Pipefy MCP to manage process management requests. Models like Claude Code utilize this connection to perform reliable project management updates.

AI-Driven workflow automation Workflows

The Pipefy server supports direct MCP connections for workflow automation. This provides Claude with the required permissions to execute project management functions.

Explore More MCP Servers

View all →