Documentation
Build one governed MCP endpoint.
Start with the tested local slice, then inspect the managed cloud and Kubernetes targets. Live cross-target portability remains an explicit acceptance test.
Guides
From first composition toward production operations.
Getting started
Run the local stack, inspect the demo tenant, register a server, and create your first composition.
02Self-hosting
Evaluate with Docker Compose or inspect the production-oriented Kubernetes target; live cluster proof is pending.
03Composition
Understand members, namespaces, aliases, versions, promotion, and rollback.
04Identity
Issue scoped gateway sessions and review preview federation wiring; connected accounts remain planned.
05Policy
Shape discovery and execution, simulate decisions, and introduce human approval.
06Security
Review trust boundaries, credential handling, tenant isolation, and disclosure policy.
Repository reference
Move from product questions to exact implementation evidence.
These maps explain when to use each maintained Markdown reference, what it covers, and where the current proof stops. The full source remains in the public repository.
Feature reference
Map every major product surface to implemented evidence, preview work, designed capabilities, and the next proof required.
R2Requirements traceability
Connect stable product-requirement families to their implementation, scoped verification, and the exact acceptance evidence still missing.
R3MCP composition lifecycle
Follow one governed endpoint from upstream registration and versioned composition through discovery, policy, execution, provenance, and audit.
R4Management console guide
Navigate the connected management console, distinguish authenticated and demo modes, and use each implemented workflow without inferring unfinished features.
R5API, SDK, and CLI reference
Use the implemented control-plane routes, MCP endpoint, response envelopes, TypeScript and Python clients, and operational CLI.
R6MCP server and connector authoring
Build an upstream MCP server that composes cleanly, with stable tools, bounded schemas, explicit side effects, safe errors, and documented security expectations.
R7Configuration reference
Configure the portable Node server, managed cloud app, static web surface, CLI, Docker Compose, Helm, and storage adapters.
R8Operations runbook
Prepare, deploy, validate, monitor, recover, and document the portable Node and Kubernetes distribution with explicit evidence gates.
R9Troubleshooting
Diagnose installation, control-plane, MCP, managed cloud, Docker, Kubernetes, readiness, audit, and incident failures from the first broken layer.
R10Development guide
Work in the monorepo, preserve the portable boundary, run quality gates, and extend domain, storage, executor, security, and documentation surfaces.
Evidence and boundaries
Read the current status before planning a production rollout.
The maintained source index covers the complete documentation set; status and limitations distinguish tested behavior from preview, designed, and blocked work.
Implementation status ↗
Reproducible evidence, acceptance scenarios, and the exact work still required.
E2Known limitations ↗
Security, consistency, identity, protocol, and operational boundaries for this snapshot.
E3Complete documentation index ↗
Every maintained product, engineering, security, identity, policy, and operations document.
Core API
A small typed surface with explicit tenancy.
Management responses include a request ID, and failures use a consistent problem envelope.
curl http://localhost:8787/api/v1/overview \
-H 'x-litemcp-tenant: org_demo' \
-H 'x-litemcp-role: finance-admin'
# Demo headers are for explicit local demo mode only.
# Production resolves tenant and role from authenticated identity.