Can AI agents automate Visma Business NXT?

Visma Business NXT is automatable today through a public GraphQL API and a vendor-hosted MCP server. This record is the cloud ERP, not on-prem Visma Business, Visma.net ERP, Visma Administration, or Tripletex. GraphQL endpoints are https://business.visma.net/api/graphql for a user context (Authorization Code with PKCE) and https://business.visma.net/api/graphql-service for a service context (client credentials). Both go through Visma Connect after an application is registered in the Visma Developer Portal. The schema exposes system and company tables with queries plus insert, update, delete, processing, and report mutations. Webhooks POST row INSERT, UPDATE, and DELETE events with table identifier and primary keys so the app can refetch via GraphQL. The first-party MCP server at https://mcp.business.visma.net/ uses streamable HTTP and Visma Connect OAuth. Reads can run any GraphQL query the signed-in user can see. Mutations are blocked in execute_graphql_query; writes go through create_entity and update_entity on a fixed table list (orders, associates, products, vouchers, and related tables). Company AI permission must allow MCP Read, and Write requires Read, in both System information and Company. Only a System supervisor can change those fields. Embedded apps use the official @business-nxt/app-messaging SDK and never see the bearer token. Zapier, Make, Power Automate, and n8n connectors were not opened. No official CLI was established. Computer-use viability is unassessed. API scores 8 and is the best path because GraphQL mutations cover every table, while MCP writes stay on the published list and need company AI opt-in.

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