Codex Report Pack Exos Systems
Generated by Codex

MCP Commercial Deployment

Customer-ready deployment guide for the Exos MCP Factory and MCP Server, including the self-contained Docker source bundle, the Compose stack, live quick links, DNS conventions, and handoff materials.

Main site Admin login System audit
Download

Download Bundle ZIP

Download the self-contained commercial handoff package, including Docker Compose, env template, reverse proxy config, and the source needed to build both services locally.
Quick link

Open MCP Factory

Launch the live Factory web interface that generates deployable MCP server code from an estate manifest.
Quick link

Check MCP Health

Confirm the live Exos MCP server is up, responding, and showing the configured backend integrations.
Endpoint

MCP Endpoint

Primary Streamable HTTP endpoint for MCP clients. This is the host customers and demos should target after deployment.
Reference

Factory User Guide

Detailed background on the Factory UI, manifest structure, and generated MCP output for implementation and onboarding.
Documentation and download

Where recipients go first

The live documentation for this deliverable is this page: https://exos.bluenotelogic.com/reports/mcp-commercial-deployment.php. The downloadable handoff package is here: https://exos.bluenotelogic.com/reports/downloads/exos-mcp-commercial-bundle-20260420.zip. That pairing should be used in customer emails so the recipient gets one explanation page and one file bundle.

Important positioning

FOSSBilling was the demo, not the platform limit

The current Exos demo uses FOSSBilling as the example billing backend, and SuiteCRM as the example CRM backend. That should not be presented as a limitation of the MCP package. The deployment model is adapter-driven: with the right manifest inputs, capability mappings, authentication, and endpoint configuration, the same pattern can be used against other target systems.

In short: FOSSBilling proved the concept in the live demo, but the deliverable should be described as backend-flexible rather than FOSSBilling-only.
Distribution model

What ships in the commercial bundle

The deployment pack now follows the clean commercial pattern we wanted: one self-contained Docker bundle, one Docker Compose stack, one setup guide, one reverse proxy configuration, one optional customer configuration template, and the source required to build both services locally. The bundle mirrors the repo layout so the included Compose file works without any registry dependency.

Service 1

  • exos-mcp-factory runs the web interface and manifest-driven code generator.
  • Default internal port: 4001.
  • The hosted ZIP includes the source needed to build it locally.

Service 2

  • exos-mcp-server runs the MCP endpoint and TM Forum API layer.
  • Default internal port: 3000.
  • Reads customer-specific backend credentials from .env.
Launch steps

Recommended deployment workflow

  1. Download and extract the bundle ZIP on the Docker host, keeping the folder structure intact.
  2. Change into deployments/mcp-commercial and copy .env.example to .env.
  3. Set the customer domains, ACME email, Factory basic auth hash, and backend credentials.
  4. Run docker compose up --build -d.
  5. Verify https://factory.customer-domain.com/ and https://mcp.customer-domain.com/health.
  6. Point DNS for the customer hostnames at the Docker host if not already done.
No registry URL, image publishing step, or private pull credential is required for the hosted customer bundle. The ZIP already includes both source trees needed for local Docker builds.
DNS and env

Recommended public routing pattern

Setting Example value Purpose
FACTORY_DOMAIN factory.customer-domain.com Public hostname for the Factory web interface.
MCP_DOMAIN mcp.customer-domain.com Public hostname for the MCP server and TMF API layer.
FACTORY_BASIC_AUTH_PASSWORD_HASH $2a$14$... Caddy password hash protecting the Factory UI.
FOSSBILLING_URL https://billing.customer-domain.com Primary billing backend consumed by the MCP server.
SUITECRM_URL https://crm.customer-domain.com Optional CRM backend for care and account-management tools.
Bundle contents

Files to hand over

  • deployments/mcp-commercial/docker-compose.yml
  • deployments/mcp-commercial/.env.example
  • deployments/mcp-commercial/Caddyfile
  • deployments/mcp-commercial/README.md
  • deployments/mcp-commercial/customer-config.example.json
  • deployments/mcp-commercial/email-summary.md
  • deployments/mcp-commercial/email-executive.md
  • deployments/mcp-commercial/email-technical.md
  • mcp-server/
  • mcp-factory/
Verification

What to test after launch

  • The Factory UI loads behind basic auth and shows the customer hostname in the header.
  • The MCP health response returns the configured backend URLs and expected version metadata.
  • The MCP endpoint is reachable by the intended client or agent runtime.
  • TLS is valid on both public hostnames.
Email handoff

Two ready-to-send email drafts

The bundle now includes two email drafts: email-executive.md for leadership and customer stakeholders, and email-technical.md for implementation teams. A short index remains in email-summary.md so the delivery owner can quickly pick the right version.