Default tools for the hosted Patchworks MCP server

Introduction

The hosted Patchworks MCP server includes a default set of tools that are ready to use. These tools are summarised here, in the following categories:

• Flow management

• Data pools

• Marketplace

• Troubleshooting

• Utility

• Agent conversation - platform agents

Flow management

Tool	Summary
get_all_flows	List flows from the Core API.
get_flow_runs	Query flow runs (filter by status; started_after; sort; includes).
get_flow_run_logs	Retrieve logs for a specific flow run (optionally with payload IDs).
start_flow	Trigger a flow run via the Start service (/flows/{id}/start).

Data pools

Tool	Summary
list_data_pools	List all data (dedupe) pools.
get_deduped_data	Retrieve deduplicated data for a specific pool.

Marketplace

Tool	Summary
get_marketplace_apps	List marketplace blueprints from the Patchworks marketplace.
get_marketplace_app	Get details of a specific marketplace blueprint by ID.

Troubleshooting

Tool	Summary
summarise_failed_run	Summarise what went wrong in a failed run.
triage_latest_failures	Fetch recent failed runs and return a compact summary.
download_payload	Download payload bytes for a given payload metadata ID (base64).

Utility

Tool	Summary
example_get_all_flows	Example demonstrating tool definition patterns.
list_tools	List all available tools in this MCP server.

Agent conversations

These tools provide low-level access to the Patchworks agent conversation API. They can be used to interact with any platform agent feature directly. For purpose-built wrappers with clearer parameter guidance, see Platform agents below.

Tool	Summary
list_agent_conversations	List all agent conversations (paginated).
create_agent_conversation	Create a new agent conversation for a given feature (flow-builder, map-builder, or connector-builder).
get_agent_conversation	Get a specific agent conversation by ID.
reply_to_agent_conversation	Send a follow-up message to an existing agent conversation.

create_agent_conversation payload reference

The payload field in create_agent_conversation is feature-specific:

Feature	Payload fields
flow-builder	flow_id (int, optional) — omit to create a new flow.
map-builder	flow_step_id (int, required), flow_version_id (int, required), flow_id (int, required).
connector-builder	connector_id (int, optional) — omit to create a new connector.