Can AI agents automate Infor M3?

Infor M3 is automatable today through its MI program REST surface on the ION API Gateway, not through a first-party MCP server we can confirm. CloudSuite documentation states that more than 6,000 MI transactions expose a large part of M3 business logic as REST at tenant paths such as M3/m3api-rest/v2/execute, authenticated with OAuth 2.0 through Infor OS. Backend jobs use downloaded .ionapi credentials with the client-credentials or resource-owner service-account grants; interactive clients use authorization code. On-premises H5 environments can still use basic authentication. Transaction catalogs and Swagger live in the tenant API Gateway under Infor M3, so agents need a provisioned tenant, authorized app, and program or transaction names such as CRS610MI. ION is shared Infor OS infrastructure; this record covers only M3 MI programs, Event Hub, and M3 BOD mappings, not Infor LN or CloudSuite Industrial (SyteLine). Outbound and inbound BODs plus Data Lake Publisher give event and bulk paths. The official M3 Odin SDK and odin CLI build H5 extensions that call MI programs; they are not a general ERP shell. Make maintains an Enterprise-plan Infor M3 connector that is invoice-narrow plus a generic API call. Infor RPA has H5-specific tutorials, but no computer-use probe was run. Infor's public history states that M3 began as Intentia's Swedish Movex product, later Lawson M3, before the 2011 Infor acquisition.

Best path today: api · Overall automatability: 6/10