Account
Team server
No hosted team server yet
The hosted team server gives your whole team one shared, always-on context plane: shared workspaces, role-based access (viewer / member / admin / owner), a live event bus and a per-call audit log — reachable over MCP from every editor.
It is provisioned automatically the moment your Team subscription becomes active. Upgrade to spin one up.
Setting up your server…
Your subscription is active and we are provisioning your dedicated team server. This usually takes a minute or two (including the first TLS certificate).
Get your team started
3 steps- 1 Invite a teammate
Issue a member token under Members & tokens — each teammate (or editor) gets their own, and you can revoke any token anytime.
- 2 Connect editor & CLI
Share the snippets under Connect your tools. The new token is filled in for you — the same token works in any MCP editor (Cursor, Claude, …) and the local
lean-ctxCLI. - 3 Add knowledge & seats optional
Connect GitLab / GitHub so issues, MRs and pipelines become searchable for everyone, and scale seats as your team grows — prorated automatically.
Team ROI & usage
An aggregated, privacy-preserving roll-up of the signed savings batches your
team pushes (lean-ctx savings push) — provable tokens and cost
your team did not spend, and how that compounds over time.
Per member
Click a member for their 90-day drilldown.
Per model
Per tool
—
Top models
Top tools
Loading drilldown…
Could not load this member's drilldown. Try again.
No signed savings batches yet. Once your team runs
lean-ctx savings push, your ROI and usage trends appear here.
Hosted index storage
Your server continuously indexes the shared workspace (BM25 + graph + knowledge) plus everything your connectors ingest. This is the live on-disk footprint on the persistent volume, measured against your plan quota — it never gates reads, only pauses hosted growth at the limit.
Knowledge connectors
Connect GitLab or GitHub and your server keeps the shared knowledge base
in sync on a schedule — issues, merge / pull requests and pipelines become
searchable for every seat via ctx_semantic_search and
ctx_knowledge. Access tokens are encrypted at rest and never
leave the control plane.
+ Add a connector
Connect your tools
Issue a token under Members & tokens below — it travels as
a Bearer header, so keep it secret. The same token works
for both your editor (MCP) and your local lean-ctx CLI.
Your new token is filled into the snippets below — copy it now, it is shown only once.
1 · Editor (MCP)
Add the server to any MCP-capable client (Cursor, Claude, …).
Or call the HTTP API directly
2 · Local lean-ctx CLI
Link your local engine so your provable savings flow into the team ROI roll-up above and you can pull the org view from your terminal. Run once with a member token:
With team_auto_push on, every session syncs automatically. One-off:
lean-ctx savings push. See the roll-up with
lean-ctx savings team. New here?
Install lean-ctx →
Members & tokens
Copy it now — for security it is shown only once and cannot be retrieved later.
Invite links
Skip the token hand-off: mint a one-time link, send it to a teammate, and they get their own member token with prefilled setup commands. Links expire after 7 days, work exactly once, and consume a seat only when redeemed.
Copy it now — for security the link is shown only once and cannot be retrieved later.
Integrations
Post a weekly ROI summary (net tokens, cost avoided, measured actions, top mover) to Slack, Discord, or any webhook receiver. Sent once per ISO week, straight from your team server — real reported numbers only.
Questions? hello@leanctx.com