3:56 ProstDev | learn MuleSoft
Where MuleSoft mastery meets fun. Easy-to-follow video tutorials, AI experiments, and deep dives to level up your integration skills. 🚀
📺 Latest videos
Browse all videos →
3:56
15:21 3 AIs, 1 MuleSoft Prompt — Who Codes Like an Architect?
26:45 Claude Code vs CurieTech AI: Solving Advent of Code 2025 Days 1 & 2 in DataWeave (MuleSoft)
11:49 Handling 404 Errors in MuleSoft's Anypoint Code Builder (ACB) | Choice + Raise Error (Part 5)
36:42 MuleSoft Anypoint Code Builder (ACB) Full CRUD Tutorial | MySQL + Docker + Debugging (Part 4)
26:06 Start Implementing APIs in Anypoint Code Builder (ACB) with MySQL + Docker (Part 3)
🤖 Built for humans & AI
Every video and post here is machine-readable. Copy the Markdown straight into ChatGPT, Claude, or your editor — no scraping, no copy-pasting from a transcript box.
-
Full transcripts on every video
Each tutorial page includes the complete, cleaned-up transcript — read it, search it, or feed it to your AI of choice.
See a transcript -
One-click “Copy as Markdown”
On any video or post, hit Copy as Markdown in the toolbar and paste the whole thing into your prompt.
See an example -
The whole site, AI-ready
Add .md to any page URL for raw Markdown, or point an AI at /llms.txt to give it the entire site.
View llms.txt
✍️ Latest from the blog
SEO- and AI-friendly deep dives that pair with the videos.
AI Showdown Hard Mode: Claude Code vs MuleSoft Vibes
Hard-mode rematch of AI Showdown: MuleSoft Edition. Same API-led brief, but every architect requirement is now mandatory: specs, security, secrets, error handling, MUnit, persistence, a parent POM. Here's how Claude and MuleSoft Vibes did with nowhere to hide.
ACB deploys your app with the local port instead of 8092? Your properties are resolved at build time
Deploy to CloudHub from Anypoint Code Builder and the listener uses your local ${https.private.port} instead of 8092? ACB bakes the placeholder in at build time against your local config. Force a fresh parse with -Dmule.deployment.forceParseConfigXmls=true.
Aug 3, 2026
503s after adding the JWT Validation policy on an Omni Gateway MCP server? The "optional" JWKS fields aren't optional
Securing an MCP server on Omni Gateway with the JWT Validation policy and getting only 503s with no logs? The new-UI JWKS Caching TTL and connection timeout fields are marked optional but the policy engine treats them as required. Fill them in.
Aug 2, 2026

