<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic workato-dev-kit — Use Claude Code / Cursor to build recipes &amp;amp; connectors in Workato Pros Discussion Board</title>
    <link>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-dev-kit-use-claude-code-cursor-to-build-recipes-amp/m-p/12269#M4706</link>
    <description>&lt;P&gt;Hey everyone &lt;span class="lia-unicode-emoji" title=":waving_hand:"&gt;👋&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Recently I've been building a bunch of MCP servers with Workato, and somewhere along the way I got hooked on using AI coding agents for everything. Claude Code, Cursor — once you start, it's hard to go back to doing things manually.&lt;/P&gt;&lt;P&gt;That got me thinking: why am I still clicking through the Workato UI to build recipes? So I started trying to use coding agents for recipe development too — and immediately ran into a wall. They'd hallucinate action names, get the JSON structure wrong, or confidently suggest connectors that don't exist.&lt;/P&gt;&lt;P&gt;So I built a toolkit to fix that: workato-dev-kit — a context layer that gives AI coding agents actual knowledge of Workato's recipe format, connector behaviors, and platform features.&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/rkawaishi/workato-dev-kit" target="_blank"&gt;https://github.com/rkawaishi/workato-dev-kit&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It works as a git submodule on top of your workspace repo. Once set up, you can use slash commands like `/create-recipe`, `/create-connector`, or `/create-genie` and the AI actually produces valid Workato JSON that you can push with the&amp;nbsp;Platform CLI.&lt;/P&gt;&lt;P&gt;It covers:&lt;BR /&gt;- 316 connectors with documented actions/triggers&lt;BR /&gt;- Recipe JSON generation&lt;BR /&gt;- Workflow App and MCP server scaffolding&lt;BR /&gt;- A learning cycle that improves from your own pulled recipes&lt;/P&gt;&lt;P&gt;I've been using this in real projects and honestly it's been working pretty well — recipes come out cleaner than I expected.&lt;/P&gt;&lt;P&gt;That said... AIRO is coming. Once that's out of private preview, this whole thing might be obsolete &lt;span class="lia-unicode-emoji" title=":grinning_face_with_sweat:"&gt;😅&lt;/span&gt; But until then, happy to share what I've got.&lt;/P&gt;&lt;P&gt;Curious if anyone else here has gone down this rabbit hole — using Claude Code or Cursor alongside the Platform CLI. Would love to compare notes.&lt;/P&gt;</description>
    <pubDate>Thu, 28 May 2026 12:40:38 GMT</pubDate>
    <dc:creator>ryotaro</dc:creator>
    <dc:date>2026-05-28T12:40:38Z</dc:date>
    <item>
      <title>workato-dev-kit — Use Claude Code / Cursor to build recipes &amp; connectors</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-dev-kit-use-claude-code-cursor-to-build-recipes-amp/m-p/12269#M4706</link>
      <description>&lt;P&gt;Hey everyone &lt;span class="lia-unicode-emoji" title=":waving_hand:"&gt;👋&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Recently I've been building a bunch of MCP servers with Workato, and somewhere along the way I got hooked on using AI coding agents for everything. Claude Code, Cursor — once you start, it's hard to go back to doing things manually.&lt;/P&gt;&lt;P&gt;That got me thinking: why am I still clicking through the Workato UI to build recipes? So I started trying to use coding agents for recipe development too — and immediately ran into a wall. They'd hallucinate action names, get the JSON structure wrong, or confidently suggest connectors that don't exist.&lt;/P&gt;&lt;P&gt;So I built a toolkit to fix that: workato-dev-kit — a context layer that gives AI coding agents actual knowledge of Workato's recipe format, connector behaviors, and platform features.&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/rkawaishi/workato-dev-kit" target="_blank"&gt;https://github.com/rkawaishi/workato-dev-kit&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It works as a git submodule on top of your workspace repo. Once set up, you can use slash commands like `/create-recipe`, `/create-connector`, or `/create-genie` and the AI actually produces valid Workato JSON that you can push with the&amp;nbsp;Platform CLI.&lt;/P&gt;&lt;P&gt;It covers:&lt;BR /&gt;- 316 connectors with documented actions/triggers&lt;BR /&gt;- Recipe JSON generation&lt;BR /&gt;- Workflow App and MCP server scaffolding&lt;BR /&gt;- A learning cycle that improves from your own pulled recipes&lt;/P&gt;&lt;P&gt;I've been using this in real projects and honestly it's been working pretty well — recipes come out cleaner than I expected.&lt;/P&gt;&lt;P&gt;That said... AIRO is coming. Once that's out of private preview, this whole thing might be obsolete &lt;span class="lia-unicode-emoji" title=":grinning_face_with_sweat:"&gt;😅&lt;/span&gt; But until then, happy to share what I've got.&lt;/P&gt;&lt;P&gt;Curious if anyone else here has gone down this rabbit hole — using Claude Code or Cursor alongside the Platform CLI. Would love to compare notes.&lt;/P&gt;</description>
      <pubDate>Thu, 28 May 2026 12:40:38 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-dev-kit-use-claude-code-cursor-to-build-recipes-amp/m-p/12269#M4706</guid>
      <dc:creator>ryotaro</dc:creator>
      <dc:date>2026-05-28T12:40:38Z</dc:date>
    </item>
  </channel>
</rss>

