mcpField
P
pipefy-toolkit-setup

pipefy-toolkit-setup

github.com/pipefyAgent workflows51617 installsUpdated 2d ago
Repository

About pipefy-toolkit-setup

An onboarding skill for agents setting up the Pipefy toolkit for the first time. It guides users through choosing a connection path, installation, authentication, and verification using the canonical instructions.

Key features

  1. 01Distinguish hosted, plugin, local, and CLI paths
  2. 02Select the guide for the chosen path
  3. 03Follow the authentication flow
  4. 04Verify read access or local installation
  5. 05Check for conflicting registrations

Use cases

  1. 01Connect to Pipefy for the first time
  2. 02Choose a connection path for Claude or Cursor
  3. 03Install the toolkit on a local machine
  4. 04Verify authentication and organization access

MCP support

It covers Hosted MCP, client plugins, the local toolkit, and CLI-only setup; the CLI-only path does not register an MCP server.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/pipefy/ai-toolkit --skill pipefy-toolkit-setup

After installing, type/pipefy-toolkit-setupin Claude Code to confirm it loaded.

Bundled filesreferences/cli.mdreferences/mcp.md

Details

From the project README

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

  1. 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.

    PathInstall guide sectionOutcome
    Cursor Marketplace pluginCursor Marketplace pluginHosted server, browser sign-in, no local Python
    Hosted MCPHosted MCPHTTPS mcp.pipefy.com
    Local toolkitQuick installLocal server and CLI, including local-file tools
    Claude Code pluginClaude Code pluginMarketplace and slash install/login
    CLI onlyCLIpipefy on PATH; no MCP

  2. Execute the canonical install instructions for that path. Keep client setup and local installation aligned with the user's choice.

  3. Authenticate using the selected path's login flow.

  4. 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.

See also

Comments

Markdown supported