PRO Annual — 50 users, $106.80/year
Stop switching tabs between your automation platform and GitScrum. With this Activepieces MCP, Claude acts as a dedicated operations engineer, allowing you to manage flow credentials, monitor execution logs, and build entire business processes directly through natural language within your workspace.
Claude
ChatGPT
Cursor
Gemini
Windsurf
VS Code
JetBrains
VercelConnected via Vinkius catalog · No credit card
task.delegate()
You tell Claude, 'I need to audit our lead-generation process. Can you list all active automation flows and check the run status for the last 24 hours?'
Claude autonomously calls the `list_flows` and `list_flow_runs` tools, retrieving structured data on your active automation flows and their latest run statuses.
Claude compiles a clear report detailing which workflows are running successfully, which need immediate attention, and what steps failed. You review the status change instantly.
task.create()
Copy. Paste into a Claude-aware GitScrum task. Done.
A new sprint begins, and I need to know if all core integration flows are running without errors.
Hey Claude. Please review our main operational workflows. Use the Activepieces MCP to list all currently active automation flows and then retrieve the detailed execution data for the last five failed runs so I can debug them immediately.
Product Ops needs a new, multi-step automation flow to handle client data intake that doesn't exist yet.
Claude, we need a new onboarding workflow. First, create the folder structure for 'Client Intake'. Then, generate and activate a basic flow within it using the Activepieces MCP so I can start connecting the initial webhooks.
The external credentials for our main communication channel (Slack) are expiring, and we need to update them immediately.
I need to manage an app connection. Using the Activepieces MCP, please list all current connections. Then, find the Slack connection and use the appropriate tool to securely update its API key credentials so our automation doesn't break.
Before this capability, setting up a complex automation meant jumping between Activepieces, your API keys page, and finally back to GitScrum just to log the result. It was manual, fragile, and took half an hour of context switching every single time you needed to create a new flow or manage credentials.
Now, Claude handles that entire loop. You simply tell it in GitScrum what needs to be connected or created. The Activepieces MCP runs the necessary API calls—creating flows, listing connections, and managing folder structures—and reports back the status so you can proceed with confidence.
Open this workflow in GitScrum →Tracking automation health used to be a nightmare. You'd have to manually check the execution logs for every single flow run, hoping you didn't miss an outdated credential or a failed step that was causing downstream ticket issues.
With Claude and the Activepieces MCP, monitoring is simple. A quick prompt tells Claude to list all recent flow runs, pinpointing exactly where the process broke down and providing clear instructions on how to fix it within your GitScrum context.
claude.ask()
Claude, can you help me manage my complex automations? Use the Activepieces MCP to list all flows in the 'Marketing' folder and identify which ones haven't run successfully this week.
I just signed up for a new tool. Using the Activepieces MCP, how do I securely upsert or update its application connection credentials so Claude can use it?
Before we start development on feature X, please list all available projects using the Activepieces MCP so I know exactly what scope we are working within.
Claude, our team needs to delete an old project. Use the Activepieces MCP to ensure we get confirmation first, and then remove the entire project from the system.
tools.list()
Each tool is one operation Claude runs on your behalf.
| tool_name | operation |
|---|---|
| add_piece | Claude can call the `add_piece` function to add a custom integration piece, expanding the functionality available to your AI agent within the platform. |
| delete_app_connection | This tool lets Claude delete an existing application connection entirely if it's no longer needed for your project workflow. |
| delete_flow | Claude uses this to permanently remove an entire automation flow from your Activepieces workspace, preventing accidental execution. |
| list_flow_runs | The `list_flow_runs` tool allows Claude and your AI agent to retrieve a list of recent executions for any flow, helping you audit history. |
| update_folder | Claude can update the name of an existing folder within your workspace using this function, helping keep your automation structure clean. |
| apply_flow_operation | This tool enables Claude to apply structural changes or status updates (like moving or changing status) to a flow without manually editing it. |
| configure_git_repo | Claude can use this to configure Git synchronization for a project, ensuring that code base updates trigger necessary automation steps. |
| create_flow | This function lets Claude create an entirely new workflow or 'flow' within Activepieces, which you can then populate and test. |
| create_folder | Claude uses `create_folder` to organize your projects by creating a dedicated folder structure for related automations. |
| upsert_app_connection | This is critical: Claude uses this tool to create or update external service credentials, supporting various authentication methods like OAuth2 or basic auth. |
| upsert_global_connection | Claude can use this function to create or modify a global connection, making that credential available across multiple independent projects. |
| create_project_release | This allows Claude to programmatically create a new project release record when an automation milestone is hit. |
| create_project | Using the Activepieces MCP, Claude can initiate the creation of an entirely new project workspace within your account. |
| delete_folder | Claude uses this tool to completely remove a folder structure that is no longer relevant to the project's lifecycle. |
| delete_global_connection | This allows Claude to delete a global connection credential, ensuring sensitive keys are purged from the system safely. |
| delete_project_member | If needed, Claude can use this tool to remove specific team members from a project, managing permissions automatically. |
| get_flow_run | Claude gets detailed execution data for one specific flow run ID, allowing you to debug exactly where and why an automation failed. |
| get_flow | This function lets Claude fetch the full details of a single, specific workflow by its unique ID, so you know exactly what it's designed to do. |
| get_mcp_server | Claude uses this tool to retrieve the necessary MCP server configuration details for connecting your AI assistants to the platform. |
| invite_user | This allows Claude to invite a new user to either the platform or a specific project, managing team access automatically. |
| list_app_connections | The `list_app_connections` tool lets Claude list all existing application credentials, helping you audit what services are connected. |
| list_flows | Claude uses this function to retrieve a comprehensive list of every active automation flow in your workspace for review. |
| list_folders | This allows Claude to simply list the folder structure, giving you an overview of how your project automations are organized. |
| list_global_connections | Claude can use this tool to view all global credentials across the entire account, useful for high-level auditing. |
| list_project_members | This lets Claude retrieve a list of all users currently assigned as members to a specific project. |
| list_projects | A simple call that allows Claude to list every single project workspace available under your account. |
| list_records | Claude uses this tool to retrieve records from an internal data table, allowing you to audit structured information related to the workflow. |
| list_tables | This function lets Claude view a list of all available internal data tables within the platform for reference. |
| list_users | Simply lists every user account registered on the system, useful for compliance checks. |
| rotate_mcp_token | Claude can use this to rotate an MCP token for a project, which is essential security maintenance after key changes. |
| update_project | This tool allows Claude to update general settings and metadata for an entire project workspace when requirements change. |
| update_record | Update a specific record |
grade
A+
tools
32
auth
Required
catalog
Vinkius
faq.read()
Free for small teams. Set up in 5 minutes. Cancel anytime.
GitScrum lists this MCP as a Vinkius partner. Installations happen on Vinkius.
Connect GitScrum with the tools your team already uses. Native integrations with Git providers and communication platforms.
GitHub
GitLab
Bitbucket
Slack
Teams
Discord
Zapier
PabblyConnect with 3,000+ apps via Zapier & Pabbly
