Home/ Tools/ XML SDK Helper
πŸ—οΈ

Mule XML SDK Helper

Build Mule XML SDK connector definitions visually. Add operations and parameters through a form, and get ready-to-paste XML without memorising the schema.

XML SDK Connectors MuleSoft 100% Client-Side
Auto-converts to kebab-case
Optional Fields
XML Output
πŸ’‘ Set the Operation name first, then switch to the Parameter tab to add parameters. Each click of "Add Parameter" appends to the output XML.

How to Use the Mule XML SDK Helper

Build complete XML SDK connector definitions visually. No schema docs needed. Just fill in the form and copy the output.

Set Operation Name

Switch to the Operation tab. Type a name and it auto-converts to kebab-case as required by the XML SDK spec. Optionally add a description.

Add Parameters

Switch to the Parameter tab. Fill in use (REQUIRED/OPTIONAL), name, display name, type, and role fields for each parameter, then click Add Parameter.

Review Live XML

The right panel updates in real-time with every change, showing the full pretty-printed <operation> block ready for your connector module descriptor.

Copy or Download

Hit Copy to paste directly into your module-info.xml, or Download to save as an .xml file for later reference.

Frequently Asked Questions

What is the Mule XML SDK?
The Mule XML SDK is a framework for building custom MuleSoft connectors using XML descriptor files and Java code. It lets teams create reusable, published connectors for internal or public use in Anypoint Exchange, without the complexity of the older DevKit approach.
What are the Operation and Parameter tabs for?
An Operation is a single action your connector exposes (e.g., "get-records", "send-message"). Parameters are the inputs that operation accepts (e.g., a query string, a timeout, a payload). This tool helps you configure both and generates the correct XML block for your module-info.xml.
What does the "Role" field mean?
Role controls how the parameter appears in the Anypoint Studio UI: BEHAVIOUR makes it an attribute field (small config option), CONTENT makes it a content/body input (e.g., payload), and PRIMARY marks it as the main connector input at the top of the config panel.
Can I add multiple parameters to one operation?
Yes. The tool is designed for this. Fill in and click Add Parameter for each field. Each one is appended to the live XML output. You can add as many parameters as your operation needs.
Why is my name auto-converted to kebab-case?
The XML SDK specification requires operation and parameter names in kebab-case (e.g., my-operation, not myOperation). The tool converts your input automatically so you don't have to remember the convention.
What happens when I click Reset All?
Reset All clears the entire operation, including its name, description, and all added parameters. The XML output is wiped so you can start fresh with a new operation definition from scratch.

From the Blog

In-depth articles on MuleSoft connector development and integration patterns.

🀠 Find this tool useful?

Connector development is hard. This tool takes away the boring parts. If it helped, a coffee shows your support and keeps this toolkit growing!