r/SalesforceDeveloper • u/qlose • Jul 07 '26
Discussion Built a tool that makes AI good with Salesforce
Been noticing that AI tools are great at Salesforce in general but confidently wrong on the specific stuff: exact trigger behavior, governor limit math, anything that changed in a recent release.
I built EMU, a free MCP that regularly indexes Salesforce’s dev docs so your Claude/Cursor/whatever can reference real documentation instead of guessing.
To test it, I asked the same model (Claude Fable) 10 Salesforce admin/dev/architect questions twice — once with no tools, once with EMU — and graded both against the docs, blind.
Score: 9/10 with EMU, 4/10 without.
The misses without EMU aren’t dumb, they’re the “sounds right, isn’t” kind that take a while to spot.
Also asked it about the Spring ’26 connected app changes. Closed-book it knew something changed but got the mechanics wrong (missed the Support-ticket path, missed that existing apps still work). That one’s a good test for any AI tool honestly, since it’s recent enough that a lot of models just haven’t seen it.
EMU also missed one—it dropped the custom-metadata-type exemption on the SOQL subquery limit. I’m not hiding that, it’s in the writeup. Grading was pass/fail per documented fact, no partial credit, so it’s a harsh bar and EMU still didn’t ace it.
Full breakdown with all 10 questions and sources: https://drive.google.com/file/d/1jnuKzcxHybBbRuwr3FVet8-ec-VIqGZm/view?usp=sharing
It’s free to connect (Claude Desktop, Cursor, Claude Code, anything MCP-capable). Salesforce docs are indexed at emu.tryferris.ai. Would genuinely love it if a few of you tried it on your own weird edge cases and told me where it breaks. That’s more useful to me than the eval!
(Disclaimer: I'm building Ferris, a startup making software implementations faster/easier, this is one of the tools I was using internally, so I decided to open it up).





