pipefy-toolkit-setup
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChinesePipefy toolkit setup (first-time onboarding)
Pipefy工具包设置(首次入门)
Canonical install snippets live only in the root (#246: no second god-doc of commands). This skill is the agent checklist — print or run the README blocks verbatim; do not invent alternate commands.
README.md#installationEdge cases: . Auth: . Env: .
packages/mcp/README.mddocs/cli/auth.mddocs/config.md标准安装代码片段仅存在于根目录的中(#246:请勿重复编写命令文档)。本技能是Agent的检查清单——请一字不差地打印或运行README中的代码块;请勿自行编写替代命令。
README.md#installation边缘情况参考:。认证相关:。环境配置:。
packages/mcp/README.mddocs/cli/auth.mddocs/config.mdWhen to use
使用场景
- "Set up Pipefy", "install the MCP", "connect Claude/Cursor to Pipefy"
- User mentions ,
/plugin marketplace add, or/pipefy:installmcp.pipefy.com - Fresh machine with no on PATH and no Pipefy MCP server
pipefy
Do not use once tools already work — switch to a domain skill (pipes, tables, …).
- 用户提出“设置Pipefy”、“安装MCP”、“将Claude/Cursor连接到Pipefy”等需求
- 用户提及、
/plugin marketplace add或/pipefy:installmcp.pipefy.com - 新机器上未配置环境变量,且未部署Pipefy MCP服务器
pipefy
请勿在工具已正常工作后使用——此时应切换到领域技能(如管道、表格等)。
Prerequisites
前置条件
- User has a Pipefy account (Admin access if they need a service account).
- Hosted MCP: Claude Code CLI ().
claude - Local toolkit: a shell that can run (
curlcan installinstall.sh).uv
Who does what
| Actor | Does |
|---|---|
| Agent | Asks path; prints README commands verbatim; runs shell |
| User types | Claude slash commands ( |
| User in browser | OAuth for hosted ( |
- 用户拥有Pipefy账户(如需服务账户则需管理员权限)。
- 托管MCP:需安装Claude Code CLI()。
claude - 本地工具包:需支持的Shell环境(
curl可安装install.sh)。uv
角色职责划分
| 角色 | 职责 |
|---|---|
| Agent | 询问用户选择的路径;一字不差地打印README中的命令;在用户同意时运行Shell命令 |
| 用户输入 | 输入Claude斜杠命令( |
| 浏览器端用户 | 完成托管模式的OAuth认证( |
Tools needed
所需工具
Setup is outside the Pipefy MCP tool surface. After auth succeeds, verify with:
| Tool (MCP) | CLI equivalent | Read-only |
|---|---|---|
| | Yes |
| | Yes |
设置过程在Pipefy MCP工具范围之外。认证成功后,可通过以下方式验证:
| 工具(MCP) | CLI等效命令 | 是否只读 |
|---|---|---|
| | 是 |
| | 是 |
Steps
步骤
-
Choose one path — ask the user; do not pick silently.If they only say “Claude Code” (no path), ask a closed question:Hosted MCP (zero local Python,) or the Claude Code plugin (slash commands + local CLI)? If you’re unsure, Hosted is the usual first try.
mcp.pipefy.comPath README section Outcome Hosted MCP Hosted MCP HTTPS (remote-safe tools)mcp.pipefy.comLocal toolkit Quick install → local server + CLIinstall.shClaude Code plugin Claude Code plugin Marketplace + slash install/login CLI only CLI on PATH; no MCPpipefyNever register both hosted HTTP and local stdio/plugin under the MCP server name.pipefy -
Execute the chosen README block — run it in the shell, or print it for the user to paste (required for Claude slash commands). Do not reorder the plugin sequence: marketplace →→
/plugin install pipefy→/pipefy:install./pipefy:pipefy-login -
Auth — hosted: finish the client browser OAuth prompt (if status is Needs authentication). Local/plugin/CLI:
claude mcp login <name>orpipefy auth login(see README). Service accounts:/pipefy:pipefy-login.docs/config.md -
Verify
- Shell (local / plugin / CLI):
pipefy --version - MCP: call (needs no id — the natural first read; confirms the credential works and surfaces the org ids other tools need) or another read-only tool the user allows
list_organizations - Confirm exactly one MCP registration for the path you chose (hosted vs plugin)
pipefy
- Shell (local / plugin / CLI):
-
选择一种路径——询问用户,请勿自行决定。如果用户仅提及“Claude Code”未指定路径,请提出封闭式问题:选择托管MCP(无需本地Python环境,使用)还是Claude Code插件(斜杠命令+本地CLI)?若不确定,托管模式通常是首次尝试的首选。
mcp.pipefy.com路径 README对应章节 结果 托管MCP Hosted MCP 使用HTTPS协议的 (远程安全工具)mcp.pipefy.com本地工具包 快速安装脚本 通过 搭建本地服务器+CLIinstall.shClaude Code插件 Claude Code插件 插件市场+斜杠命令安装/登录 仅CLI CLI 加入环境变量;无MCPpipefy请勿同时注册托管HTTP和本地标准输入输出/插件两种模式的MCP服务器,并命名为。pipefy -
执行所选README中的代码块——在Shell中运行,或打印给用户粘贴(Claude斜杠命令必须如此操作)。请勿调整插件安装顺序:插件市场 →→
/plugin install pipefy→/pipefy:install。/pipefy:pipefy-login -
认证——托管模式:完成客户端浏览器的OAuth提示(若状态为“需要认证”则执行)。本地/插件/CLI模式:执行
claude mcp login <name>或pipefy auth login(详见README)。服务账户配置参考:/pipefy:pipefy-login。docs/config.md -
验证
- Shell环境(本地/插件/CLI):执行
pipefy --version - MCP:调用(无需ID——这是最自然的首次只读操作,可确认凭证有效并显示其他工具所需的组织ID)或用户允许的其他只读工具
list_organizations - 确认仅注册了所选路径对应的一个MCP(托管或插件模式)
pipefy
- Shell环境(本地/插件/CLI):执行
Success criteria
成功标准
- One active Pipefy MCP registration for the chosen path (or CLI-only with no MCP).
- Auth completed.
- Read-only MCP call or succeeds.
pipefy --version
- 所选路径对应一个活跃的Pipefy MCP注册(或仅CLI模式无MCP)。
- 认证完成。
- 只读MCP调用或执行成功。
pipefy --version
Failure modes
故障排查
| Symptom | Likely cause | Recovery |
|---|---|---|
| Slash commands missing | Plugin not installed | README Claude Code plugin — marketplace + install first |
Two | Hosted + plugin both registered | |
| OAuth not finished | |
| CLI not on PATH | |
| MCP tools empty / auth errors | Login not done | Re-run login; service accounts → |
macOS | Keychain write | |
| 症状 | 可能原因 | 解决方法 |
|---|---|---|
| 斜杠命令缺失 | 未安装插件 | 参考README中的Claude Code插件章节——先进入插件市场安装 |
存在两个 | 同时注册了托管和插件模式 | 执行 |
| 添加托管MCP后显示“需要认证” | 未完成OAuth | 执行 |
提示 | CLI未加入环境变量 | 执行 |
| MCP工具为空/认证错误 | 未完成登录 | 重新执行登录;服务账户配置参考 |
macOS系统提示 | 钥匙串写入问题 | 参考 |
See also
相关链接
README.md#installationskills/README.md
README.md#installationskills/README.md