Apache 2.0Pre-1.0 · managed cloud and self-hosted previewsRead the open-source commitment
LiteMCPComposer
Open console
HomeProductComposerRegistryIdentityPolicyRoutingObservabilityOn-premManaged cloudOpen sourceDocsPricingEnterpriseSecurityChangelogBlog

Documentation

Self-hosting and Kubernetes

Evaluate LiteMCP Composer locally, then inspect the production-oriented Helm target. A live Kubernetes product journey has not yet passed.

Self-hosted preview

Images build and Helm profiles lint/render without a managed cloud dependency. No live cluster install, readiness, MCP, recovery, upgrade, or disconnected test has passed yet.

Production-oriented target topology

The target separates these responsibilities. Status describes the current repository evidence:

ComponentResponsibilityStatus
WebAstro management and documentation surfaceAvailable now
Control planeRegistry, composition, identity, policy, sessions, audit, and OpenAPIPreview
GatewayStreamable HTTP tools, discovery filtering, policy recheck, and upstream executionPreview
MongoDBTenant-scoped control-plane records and audit metadataPreview
Secret providerEnvelope keys and durable upstream credentialsPlanned
Telemetry stackOpenTelemetry traces, metrics, logs, and SIEM exportPlanned

Docker Compose evaluation

cp deploy/docker-compose/.env.example deploy/docker-compose/.env
# Replace BETTER_AUTH_SECRET in the copied file.
pnpm docker:up

The evaluation topology is not a substitute for production secret management, backups, network policy, or high availability.

Preflight for Kubernetes

Before treating a future release as production-ready, validate:

  • Ingress hostnames, TLS certificates, and trusted proxy headers
  • Replica-set connectivity, authentication, storage class, and backup target
  • Secret references, KMS or Vault access, and key-rotation ownership
  • OIDC/SAML redirect URIs, issuer reachability, and SCIM credentials
  • Network policies and approved upstream egress
  • OpenTelemetry collector and SIEM delivery

Render and install the Helm chart

The lint and template steps are validated. The install command is an operator preview and has not been exercised against a live cluster in this repository snapshot.

helm lint deploy/helm/litemcp
helm template litemcp deploy/helm/litemcp \
  --namespace litemcp \
  --values values.production.yaml

helm upgrade --install litemcp deploy/helm/litemcp \
  --namespace litemcp \
  --create-namespace \
  --values values.production.yaml \
  --atomic \
  --timeout 10m

Keep secrets out of the values file. Reference Kubernetes Secrets or an external secret operator backed by your vault or KMS.

Required operating routines

  • Test database and credential-metadata backups on a schedule.
  • Practice restore into an isolated namespace and verify audit-chain continuity.
  • Render every upgrade, inspect migrations, and preserve rollback artifacts.
  • Rotate session, service, and credential-encryption keys with overlapping validity.
  • Collect diagnostics without tool arguments, tool results, tokens, or provider secrets.

Restricted and air-gapped environments

The intended release process mirrors pinned container images, Helm charts, SBOMs, signatures, and release manifests into an approved internal registry. Signed release artifacts do not yet exist, and no disconnected test has passed. Connector packages that need internet APIs remain subject to the environment's approved routes.

Operational support

The software and deployment assets remain free. Planned enterprise services may later provide architecture review, installation, migrations, LTS planning, recovery exercises, security response, and agreed support terms. No SLA is published today.