Volt MX Foundry Installation on Single Node and Multinode
You are here: Volt MX Foundry Installation on Single Node and Multinode
Volt MX Foundry Installation on Single Node and Multinode
You can install Volt MX Foundry in a domain mode (multinode) or a standalone mode (single node) on a local environment.
The following table details Volt MX Foundry installation supported for a single node and multinode installations.
| Volt MX Foundry Components can be installed | Single Node | Multinode |
|---|---|---|
| Console | ||
| Workspace |  |
|
| Accounts | |
|
| Identity | |
|
| Integration | ||
| Admin | |
|
| Middleware | |
|
| Services | |
|
| Metrics | |
 |
| API Developer Portal | |
|
| Engagement Services | |
|
MCP Server topology
- Single-node: The MCP Server runs on the same host as Foundry and points at the local Foundry base URL. This is the default and recommended topology.
- Multinode: MCP is installed on one node only. It must be configured to reach the Foundry load-balancer / public URL over HTTPS. To share OAuth state and refresh context across restarts, set the state store backend to Redis and provide a reachable
MCP_REDIS_URL. - MCP itself does not participate in the Foundry cluster. To make it highly available, front it with a reverse proxy or load balancer that terminates TLS and forwards to the MCP port (default 9093).
Scope reminder:
- MCP is supported only with the bundled Tomcat and bundled JBoss application servers. It is not available with WebSphere or WebLogic, and is not supported on external / pre-existing Tomcat or JBoss installs.
- The MCP Server requires HTTPS on the Foundry base URL.
- The target machine must have Python 3.12 – 3.13 with pip on the same interpreter (
python -m pip --versionmust succeed and report the same version). - MCP is never auto-selected. It must be explicitly enabled.