Apache 2.0Pre-1.0 · managed cloud and self-hosted previewsRead the open-source commitment
LiteMCPComposer
Open console
HomeProductComposerRegistryIdentityPolicyRoutingObservabilityOn-premManaged cloudOpen sourceDocsPricingEnterpriseSecurityChangelogBlog
Multiple MCP sources converging into one governed endpoint.

MCP-native enterprise composition

LiteMCPComposer

One governed MCP endpoint for every user and agent.

Purpose-built around MCP servers, capability schemas, sessions, and tool execution. Compose every upstream behind one stable contract, govern each call, and keep the deployment yours.

Open the consoleStart self-hosted
01 Apache-2.002 Identity federation preview03 Cloud · Kubernetes targets04 No required call-home

The operating model

Your clients see one endpoint. Your platform team keeps every control.

LiteMCP Composer treats composition, protocol behavior, identity, policy, routing, and evidence as one MCP-native system—not disconnected proxy rules.

Protocol-specific depth

Composition is a governed graph, not a list of proxy routes.

Every published endpoint has an inspectable path from client session to capability, policy decision, selected upstream, and final audit event.

01 / Compose · Available nowVersioned graph + namespaces

Pinned upstream references, explicit aliases, and collision handling keep the public capability surface stable.

02 / Session · Available nowScoped MCP endpoints

Short-lived sessions bind subject, organization, environment, composition, audience, and expiry.

03 / Discover · Available nowIdentity-scoped capability list

Discovery returns only the tools allowed for the resolved principal and current policy version.

04 / Invoke · PreviewOne policy at list and call

Invocation repeats enforcement and can pause a sensitive request; independent approval decisions and resume remain planned.

05 / Route · PlannedEligible, healthy upstreams

Explicit upstream dispatch exists; identity-, health-, region-, and residency-aware route selection remains planned.

06 / Prove · PreviewProtocol provenance + audit

Correlation ties namespace resolution, policy, routing, upstream execution, and outcome into one evidence trail.

Managed cloudDocker + KubernetesShared portable packages · cross-target parity test still pending

Why LiteMCP Composer

Aggregation is the start. Trust is the product.

A useful control plane must make composition reversible, identity precise, policy explainable, and operations observable.

01Preview

Version the composition graph

Pin upstream versions, resolve capability namespaces, and publish a stable MCP endpoint without hiding its provenance.

02Preview

Preserve MCP protocol fidelity

Keep capability schemas, JSON-RPC semantics, request correlation, cancellation, and explicit protocol errors intact.

03Preview

Scope discovery to identity

Bind workforce and workload principals to short-lived composition sessions, then apply the same policy at list and call.

04Preview

Govern the upstream route

Pause sensitive requests before dispatch and retain provenance plus audit evidence; health-aware route selection remains planned.

A verified identity passing through layered policy gates to a filtered set of approved capabilities.
Decision path / 01Identity and request context move through the same policy boundary used for discovery and execution.

Identity becomes policy context

One principal. One explainable decision path.

LiteMCP Composer resolves the human or workload behind a request, carries organization context forward, and exposes only the capabilities that identity is allowed to use.

  1. 01
    Resolve the principal

    Authenticated subjects and scoped sessions work today; live enterprise group and claim mapping remains preview work.

  2. 02
    Filter discovery

    Disallowed tools stay out of the capability surface instead of relying on client behavior.

  3. 03
    Enforce execution

    The policy is evaluated again at invocation, with approval required for sensitive work.

Explore identity and sessions

The platform

Seven MCP-native planes. One open roadmap.

Available, preview, and planned capabilities are labeled on each product page. The architecture keeps managed cloud infrastructure out of the portable product core.

Explore the platform
01Preview

Composer

Composer is a working preview for namespaced, version-pinned tool composition. Cross-target import, full protocol objects, and release promotion still require end-to-end proof.

02Preview

Registry

The current registry preview tracks server metadata and version pins. It does not yet provide a complete artifact or skill lifecycle.

03Preview

Identity

The identity preview binds an authenticated subject to organization context and a short-lived MCP session. It does not yet broker upstream credentials.

04Preview

Policy

The current policy slice filters tool discovery, rechecks execution, and explains deterministic decisions. Authoring and distributed activation are still preview work.

05Planned

Routing

The gateway currently dispatches to an explicit eligible member and avoids replay after an ambiguous side effect. A full route evaluator is not yet implemented.

06Preview

Observability

Request-correlated, redacted audit metadata is available now. OpenTelemetry, SIEM delivery, SLOs, and externally anchored evidence remain roadmap work.

Policy at two boundaries

What a user cannot call, they should not discover.

The gateway shapes capability discovery for the current principal, then makes the same policy decision again when an execution arrives.

See policy controls
policy.yamlversion 12
defaultEffect: deny

rules:
  - id: allow-support-read
    effect: allow
    roles: [support]
    tools: [crm.search, docs.read]
    actions: [discover, execute]

  - id: approve-financial-write
    effect: require-approval
    risks: [financial, destructive]
    actions: [execute]

One open product

One open codebase. Two deployment targets in preview.

The repository is pre-1.0. Capability status is shared across deployment targets; enterprise services are intended to fund accountable deployment and operations, not closed features.

Managed cloud · Preview

Managed cloud target

$0 / intended community model

The Worker bundle and local data migration build; no public operated service is claimed yet.

  • Cloudflare-backed deployment source
  • Wrangler dry-run and local D1 migration
  • Fair-use thresholds planned before availability
Managed cloud details
Your infrastructure · Preview

Self-hosted source

$0 / Apache 2.0

Build the portable server and web images without a managed cloud account or license server.

  • Tested local vertical slice
  • Docker images and rendered Helm profiles
  • Identity federation and SCIM wiring in preview
Self-hosting guide
Accountable operations · Planned

On-prem services

Custom / scoped engagement

Scope future installation, upgrade, HA, security, migration, and response commitments.

  • Architecture and deployment services
  • Future LTS and patch commitments
  • Air-gapped and private-cloud operations
Enterprise services

Deployment portability

Shared architecture now. Runtime parity still to prove.

The managed cloud target currently uses Cloudflare infrastructure. The portable Node.js runtime targets Docker and Kubernetes. Both compose the same core packages, but a live cloud-to-on-premises export/import journey has not yet passed.

Managed cloud preview
Worker bundle, KV/D1 adapters, and static site build.
Self-hosted preview
Portable Node/Mongo images and rendered Kubernetes chart.
Acceptance gate
Live export/import and identical gateway journey across both targets.
Compare deployment paths
One portable LiteMCP Composer configuration branching to managed cloud and self-hosted deployments.
Runtime path / 02One portable contract targets managed cloud and customer-owned infrastructure; live parity remains to be proved.

Start with the MCP servers you already use.

Register an upstream, compose a stable endpoint, simulate policy, and issue a scoped session.

Open consoleRead the quickstart