Patchworks MCP

Introduction

MCP (Model Context Protocol) is an open protocol that enables secure, standardised connections between Al assistants (e.g. Claude, Gemini, Chatgpt) and external data sources or tools (such as Patchworks).

The Patchworks MCP server acts as a bridge between an Al assistant and Patchworks. It allows the Al to interact with Patchworks, with precise control over what it can see and do. At a high level:

• MCP uses a client-server model, where an AI agent (the client) makes requests to an MCP server.

• The MCP server defines and exposes tools (e.g. get flow runs, summarise failed run, triage latest run failures) and resources (e.g. documentation, databases).

• AI agents use these tools and resources to perform actions, thereby expanding their abilities beyond their core language understanding.

You can see this in the illustration below:

This opens the door to a range of possibilities. Your AI assistant can interact with Patchworks directly to triage issues, generate reports, and even run flows - all in natural language. Whether you’re a merchant, partner, or developer, Patchworks MCP transforms how you work with your integrations.

Why Patchworks MCP?

• AI-ready iPaaS Make integrations conversational and intelligent.

• Faster troubleshooting Automate triage & identify solutions

• Customisable Add your own tools alongside our pre-loaded set

• Safe & secure Per-tenant isolation, role-based access, and auditable tool calls.

• Future-proof Works with Claude, Gemini, ChatGPT, and any MCP-compatible client.

Implementation

We provide two implementation paths for the Patchworks MCP - local and hosted:

Type	Implementation	Pros	Cons
Local	Clone a Patchworks MCP repository to retrieve setup files, then install dependencies before configuring your environment and MCP installation.	Complete control over the hosting environment.	Technical implementation and ongoing maintenance. Default tools cannot be customised.
Hosted	Minimal setup outside of the Patchworks dashboard and your AI assistant.	Less technical implementation; automatic updates; customise and deploy tools via the Patchworks dashboard.	No control of the hosting environment.

Our product documentation can also be integrated with AI assistants via an MCP server! For details, please refer to the Patchworks product documentation MCP server section.

Demo

Before looking at MCP in more detail, let's see how it can work in practice. The video below shows Claude identifying failed process flow runs from a given time period, summarising those flow failures, identifying failure patterns, recommending possible solutions, retrying failed runs, and reporting back on the outcome.