- FAC tools, same names and arguments
- 24
- tests on a separate v16 bench
- 269
- end-to-end cases over HTTP
- 80
- commit tools, by default
- off
Why
Until October 16, Aria and our catalog agents read and drafted in ERPNext through Frappe Assistant Core (FAC), a third-party Frappe app that serves an (The Model Context Protocol, an open standard that lets AI apps such as Claude call tools on a server. On our sites, the MCP server is how Aria, our agents and connected AI apps read ERPNext and draft in it.) endpoint. Kremio Connect, which we started on October 11, had its own MCP endpoint from day one, behind the same action layer the mobile app uses: every call runs as the caller, checks permissions itself and writes an Action Log row. That made two MCP servers on every site, with different rules.
On October 15 Nikolas asked for FAC to go, replaced by our own server with all of FAC’s tools.
Same names, our own code
Kremio Connect 0.4.0’s MCP endpoint serves all 24 tools of FAC 2.5.1, with the same names and arguments: documents, search, reports, workflow, data analysis and dashboards. Agents’ tool allowlists, the catalog’s honesty check and Aria’s tool patterns all reference those names, so they kept working, and clients only changed the URL. The tools run through Kremio Connect’s runner, so each call is checked against the caller’s permissions, runs inside a savepoint and writes an Action Log row.
- Commit tools are behind a Kremio Settings switch, off by default. That covers submit, cancel, workflow actions and deletes.
- Two System Manager tools that run code or SQL are behind a second switch, also off by default. They run in a child process with a read-only database session, resource limits and RestrictedPython.
- Any tool can be switched off, or limited to roles, per site.
- MCP prompts and resources came across too, with our own text.
Standard MCP clients also needed three OAuth fixes on Frappe v16, which FAC had carried its own versions of. Frappe reads an HTTP Basic header as an API key, so client_secret_basic at the token endpoint got a 401. Registration stores redirect URIs one per line, but the check splits them on spaces. And registration answers didn’t list the refresh-token grant.
We tested it on a separate v16 (Frappe's command-line tool, and the folder of apps and sites it manages. It installs apps, builds assets, migrates sites and runs tests.): 269 tests, plus an 80-case end-to-end run over HTTP that covered every tool, both switches in both positions, attempts to break out of the sandbox (all refused) and both MCP protocol revisions.
Taking an app off a running site
The control plane chooses the MCP path per site: Kremio Connect’s for a site that reports Kremio Connect 0.4.0 or newer, FAC’s otherwise, so sites could move one at a time. The (The server image every Infinary site runs: Frappe, ERPNext and our own apps, pinned to exact versions and tested together.) build now refuses a versions.json that still has a FAC entry. Before the uninstall we checked what our own site would lose: only FAC’s own 8 prompt templates and 24 built-in skills, nothing anyone had made.
How the day went
The changes across five repositories were ready a little after 7 am on October 16. Three minutes earlier, GitHub Actions had stopped running jobs for our organization (that story). So they merged late that morning on local test runs, and the golden image without FAC was built on Cloud Build instead. By late afternoon our own site ran Kremio Connect 0.4.0 and Infinary Controls 0.13.0, and Aria’s tool calls went through the new server.
Later that day, with Nikolas’s yes, the Claude app on his phone, connected to our own site, was asked in plain words to create a contact, and did. Kremio Connect’s Action Log row shows the MCP channel, a draft-class action, and Nikolas as the user.