ERPSmith
ERPSmith logo: a hammer striking an anvil in a shower of sparks

ERPSmith

The AI dev copilot for ERPNext.

Build, debug and fix DocTypes, scripts and workflows from Claude over the Model Context Protocol. Every change waits behind a plan you approve, and it remembers how your site works. Frappe v15 and v16. Free and open source (MIT).

Connect Claude to a site with OAuth, then add a field to Customer behind a plan you approve (2:23).

Up and running in three steps

  1. Install the app

    bench get-app https://github.com/abhinavprakash1992/erpsmith
    bench --site your-site install-app erpsmith
    bench --site your-site migrate

    On Frappe Cloud, install it from the Marketplace.

  2. Connect Claude

    Add a custom connector with your site's MCP address:

    https://<your-site>/api/method/erpsmith.mcp.handle

    No keys, no secrets: you sign in on your own site with OAuth.

  3. Ask

    • "Why does my Sales Invoice server script fail on submit?"
    • "Add a Region select field to Customer and show it in the list."
    • "Why can't Accounts User open Payment Entry?"

What you get

59 developer tools

DocTypes and fields, client and server scripts, workflows, permissions, print formats, reports, notifications and dashboard charts, plus debug and fix tools for each.

A plan gate

Every change is rejected until you have read and approved a plan that names it exactly. Approved changes are single-use and expire.

Runs as your user

Every tool runs with the signed-in user's roles and permissions. Give the assistant its own user and it can do exactly what those roles allow.

Memory that learns

Ships with 109 notes on Frappe sandbox rules, patterns and known fixes. You and the assistant add your company's own context.

Knows your site

Searches an index of your DocTypes (custom fields included), workflows, scripts and print formats, plus the ERPNext manual.

Private by design

Everything stays in your site's database. No telemetry, no hosted service. Privacy policy.