Nobody installs an MES from a website. An integrator does it, an ERP partner brings the customer, an agent builder needs a plant to point at. The project is Apache-2.0 so all three can make a living on it without a licence from anyone. What follows is how each is welcomed, and the one rule for being listed.
Your deliverable to the customer is a plant pack and a tag map: config, never a fork. A repeatable deploy, a backup and upgrade page with a rollback line, and a stated support policy for what 0.x means are all in the operate book, because they are what you need before betting a customer on it.
Listing rule: one merged plant pack or driver contribution. Alphabetical, no ranking, no fee, no certification, no exclusivity. When three are listed, a quarterly call replaces guessing at the roadmap.
packs/contrib/ · label partner:integrator · issues from a real line firstERPNext's own maintainers wrote the missing-MES list, and the connector fills it: machine data, OEE, downtime and SPC feeding a system that stops at work orders. The ERPNext module ships in the package; a Frappe Marketplace app is the next step and is where Frappe partners meet it.
Odoo is the second door through OCA, when the module exists. SAP and Oracle connectors are wanted, not written; the typed contract is.
ERPNext today · Odoo/OCA next · SAP, Oracle: contract exists, module does notOne MCP server, 85 tools, filtered by what the account may do. A simulated plant with scripted faults is a plant you can point an agent at without a factory, and the eval harness grades it against known truth: naming the symptom alongside the cause fails.
The server is registered under com.factorysemantics/mes. Show what your agent did in a Show-and-tell discussion; the transcripts are the content.
None yet: the project went public with simulated plants only, and the list is kept honest. The first name here will be the first real line. If you want that to be you, say so below or in the Who is using it thread.
This is not a partner portal. It is one form that reaches one person, who replies to each. What it does: puts you on the list that hears first when the connector, the pack path or the integrator page changes, and starts a conversation about the first customer.
What it never does: charge, rank, or ask for exclusivity.