Pipefy Toolkit Setup

Organization

pipefy

pipefy-toolkit-setup

Guide a first-time user through Pipefy AI toolkit setup (Cursor Marketplace plugin, hosted MCP, local install.sh, or Claude Code plugin). Use when the user asks to install Pipefy MCP, connect Claude/Cursor to Pipefy, run /pipefy:install, or set up mcp.pipefy.com. Do not use for day-to-day Pipefy workflows after MCP is already working.

Overview

Publisher	pipefy
Repository	`ai-toolkit`
Skill name	`pipefy-toolkit-setup`
Stars	52
Forks	24
Bundled files	2
License	Apache-2.0
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by pipefy on GitHub. Read the source before you install it.

Installation

Install the Pipefy Toolkit Setup AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/pipefy/ai-toolkit/tree/main/plugins/pipefy/skills/pipefy-toolkit-setup
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/pipefy/ai-toolkit/tree/main/plugins/pipefy/skills/pipefy-toolkit-setup

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/pipefy/ai-toolkit.git /tmp/ai-toolkit
mkdir -p .claude/skills
cp -r /tmp/ai-toolkit/plugins/pipefy/skills/pipefy-toolkit-setup .claude/skills/pipefy-toolkit-setup

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Pipefy Toolkit Setup in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Pipefy Toolkit Setup on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Pipefy Toolkit Setup is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Pipefy toolkit setup (first-time onboarding)

Choose a connection path below, then read the MCP reference or CLI reference for that path. Load only the relevant reference.

Canonical install snippets live in docs/install.md. The root README has a quick-start table with the first command for each install path. This skill is the agent checklist: print or run the install-guide blocks verbatim, and do not invent alternate commands.

Edge cases: packages/mcp/README.md. Auth: docs/cli/auth.md. Env: docs/config.md.

When to use

“Set up Pipefy”, “install the MCP”, or “connect Claude/Cursor to Pipefy”.
The user mentions a client plugin, a hosted connection, or a fresh machine without toolkit access.

Do not use once tools already work — switch to a domain skill (pipes, tables, …).

Prerequisites

User has a Pipefy account (Admin access if they need a service account).

Steps

Choose one path — ask the user; do not pick silently. Respect whether they want a hosted connection, a client plugin, a local toolkit, or CLI only.

If they only say “Claude Code”, ask: Hosted MCP (zero local Python) or the Claude Code plugin (slash commands and local CLI)? If unsure, suggest Hosted.

If they only say “Cursor”, ask: Cursor Marketplace plugin (hosted, no local Python) or Quick install (local CLI and tools that read local files)? If unsure, suggest the plugin.

Path	Install guide section	Outcome
Cursor Marketplace plugin	Cursor Marketplace plugin	Hosted server, browser sign-in, no local Python
Hosted MCP	Hosted MCP	HTTPS `mcp.pipefy.com`
Local toolkit	Quick install	Local server and CLI, including local-file tools
Claude Code plugin	Claude Code plugin	Marketplace and slash install/login
CLI only	CLI	`pipefy` on PATH; no MCP

Execute the canonical install instructions for that path. Keep client setup and local installation aligned with the user's choice.
Authenticate using the selected path's login flow.
Verify access with a permitted read-only organization operation (list_organizations needs no id and surfaces organization ids), or the local installation check. Check for conflicting registrations using the selected reference.

Success criteria

Exactly the selected connection is configured, with no conflicting registrations; CLI-only needs no server registration.
Authentication completed.
The permitted read-only operation or local installation check succeeds.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/cli.md2 KB
references/mcp.md7 KB

Frequently asked questions

What does the Pipefy Toolkit Setup AI skill do?

Why use Pipefy Toolkit Setup on TypingMind?

Because you install it once and use it with any model. Pipefy Toolkit Setup is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Pipefy Toolkit Setup in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/pipefy/ai-toolkit/tree/main/plugins/pipefy/skills/pipefy-toolkit-setup. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Pipefy Toolkit Setup?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Pipefy Toolkit Setup?

As many as you like. As long as a model supports skills, you can use Pipefy Toolkit Setup with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Pipefy Toolkit Setup AI skill free?

Yes. It is published on GitHub by pipefy under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Everything Claude Code

affaan-m

CommunityPopular

Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

Discord User Post

Post an approved message as the logged-in Discord user through the Discord desktop app. Use for release announcements or other direct user-authored Discord posts; not for OpenClaw channel sends, bots,…

Test Audit

Invoke whenever writing, changing, reviewing, or sweeping tests. Authoring gate for new tests plus audit workflow for low-value, implementation-coupled, or duplicative tests and the test-only…

Feishu Perm

Feishu collaborator and permission workflows. Activate when the user explicitly asks to inspect or change sharing, permissions, or collaborators.

Pipefy Toolkit Setup

Overview