Understand the Maxio Model Context Protocol (MCP)

The Maxio Model Context Protocol (MCP) is a secure bridge between Maxio and AI clients, including tools like ChatGPT and Claude as well as custom clients built by customers or partners. It lets an AI client reach a defined set of Maxio tools and data inside your tenant, under controls you set, rather than granting open access to your account.

If you use both Maxio Core and Advanced Billing, MCP reaches across contracts, customers, subscriptions, billing, invoicing, and transactions.

Key capabilities

Through MCP, an AI client can:

• List, read, and create certain objects or data in Maxio, within role-based permissions
• Retrieve or summarize Account, Transaction, or Customer data
• Automate common actions in your Maxio environment, under permission controls you set

These capabilities are available through supported AI clients such as ChatGPT (Cloud) and Claude, and through custom clients that integrate using the MCP specification.

Prerequisites

MCP is not simply a setting an administrator switches on. Three conditions have to be true before Maxio MCP appears under Integrations at all:

• Maxio has enabled the MCP feature for your account. This is a Maxio-side setting, so contact Maxio if the option is missing.
• Your Site is linked to a Maxio platform instance.
• SSO is enabled for your organization. MCP identifies each request by the signed-in user's SSO identity, so an organization that has not adopted SSO cannot use MCP.

If any of the three is unmet, the Maxio MCP option does not appear in the navigation.

Privacy and data access

An administrator has to enable and configure the integration before any AI client reaches your data, and access goes only to users authorized through the connector setup. Each request carries the identity of the person who made it, in a token that expires after one minute.

AI clients read your data on demand, only when an authorized user asks. They do not independently browse, scan, or continuously monitor it.

Your administrator controls what is reachable by enabling specific MCP tools and setting connector permissions.

Payment and bank account data

The MCP integration does not expose payment card or bank account details.

Subscription creation through MCP supports remittance-style payment collection only. Credit card and bank account collection flows are intentionally restricted.

Read-only and read-write access

You can configure the integration as read-only, or enable write actions. Write actions are optional and limited to specific workflows, such as creating customers, subscriptions, products, or sales orders.

Maxio recommends starting read-only unless your organization has a defined business need for write access. Your administrator can change the configuration at any time.

Data removal

When a Maxio Site is purged, the data held for it on the MCP server is purged with it, so removing a Site does not leave its data behind on the MCP side.

AI model training

Maxio does not use customer data accessed through MCP to train AI models.

For OpenAI services, data submitted through ChatGPT Enterprise, ChatGPT Business, and the OpenAI API is not used to train OpenAI models by default. Data handling is governed by your organization's agreement with OpenAI.

Related information

To review the access model, permissions, and governance controls in depth, see the Maxio MCP Security, Access, and Governance FAQ help article.