PortaBilling MCP Server configuration
Once your free trial/paid subscription is activated, you can deploy the PortaBilling MCP Server module.
Preparation steps
Before proceeding with the module configuration and deployment, perform the following steps:
Step 1: Configure a domain
Prepare a domain (e.g., mcp.company.com) that will be used to access the PortaBilling MCP Server.
When configuring DNS for the domain, specify the IP address depending on the location (cluster) where you deploy the module. Find the IP addresses here.
Step 2: Obtain TLS certificates for the domain (optional)
TLS certificates can be generated automatically by PortaOne using the Let’s Encrypt certification authority (CA). If you choose this option, you can skip this step.
Optionally, you can contact your trusted CA to order a TLS certificate for your domain. After you receive the TLS certificate and private RSA key files from the CA, you will be able to upload them via the Configuration UI.
Module configuration and deployment
Log in to the Add-on Mart management portal, locate your PortaBilling MCP Server subscription, and click Configure.
On the Configuration UI page that opens, fill in the configuration details and click Deploy (or Save for later to deploy it later).
The form in the Configuration UI consists of the following blocks:
General settings
Instance location – select the cloud datacenter closest to your PortaBilling server for module deployment (to minimize latency).
If none of the listed locations are close enough, please contact PortaOne Sales. Additional data centers in other locations can be activated upon request.
PortaBilling MCP Server version to deploy – choose a module version. The following options are available:
- Deploy the latest – select to deploy the most recent version of the module.
- Select from the full list – select to deploy a specific version from the full version list. Use the dropdown to pick the required version.
Domain configuration
MCP server domain – specify the domain name configured at preparation step 1, e.g., mcp.company.com. This domain will serve as the base URL for all MCP client connections.
Generate certificates with Let’s Encrypt service – select this checkbox if you want PortaOne to generate a TLS certificate for your domain automatically.
Certificate file (required if not using Let’s Encrypt) – upload the TLS certificate file and the private RSA key obtained from your trusted CA (see preparation step 2).
Realm configuration
Use this section to control the PortaBilling users who can access the MCP server. You can independently enable access for admins, resellers, customers, and accounts by selecting the corresponding checkboxes for each entity.
Clear a checkbox if you do not want users with the corresponding role, such as customer, to connect to the server.
Each entity connects to its own endpoint (admin, reseller, customer, or account self-care URL). When a realm is enabled, fill in the following fields:
- PortaBilling URL – specify the URL of the PortaBilling interface for the corresponding entity, e.g., https://billing.company.com:8444 for admins.
- Available API v2 tools – select which PortaBilling data, exposed as tools through API v2, are available via the MCP server.
- Additional API v1 tools – if you need to expose tools based on the PortaBilling API v1, add them using the Name and Value fields. Click Add
to add a row and Remove
to remove one. 
Other
Company name
– optionally specify your company name. AI agents connecting to the MCP server will see this as part of the server name.
Deployment
To deploy the PortaBilling MCP Server immediately, click Deploy. To save the configuration and deploy it later, click Save for later.
Once the module is successfully deployed, configure your AI agent to connect to the MCP server URL, which you prepared at step 1 and specified in the Domain configuration. Users authenticate with their PortaBilling credentials on the first connection.
