MCP Cloud · Bêta & governance

Hosted MCP comes after open-source trust.

The Skill is usable today. MCP Cloud is the planned hosted layer for team context, governed tool calls, usage controls and Executive FDE workflows. We intentionally do not present it as production-ready.

Honest by default · the local Skill earns trust before the hosted layer ships
mcp-beta.yaml · planned, not production
status: beta / not production-ready
method: open-source Skill first
planned:
  - tenant-aware RAG
  - governed tool calls
  - usage dashboards
  - Executive FDE workflows
hardening_required:
  - Postgres persistence
  - Redis rate limits
  - signed billing webhooks
  - strict auth + CORS
  - monitoring + load tests
Positioning

MCP is the execution layer — not the launch product.

The project earns trust through the local Skill, Docs, Academy and the public Registry. The hosted layer only adds value where teams need shared context, governed tools, auditability and collaboration.

What MCP Cloud adds

Planned hosted capabilities.

Directionally planned — not a production guarantee.

CONTEXT

Team RAG

Tenant-aware retrieval over docs, artifacts, examples and field memory.

TOOLS

Governed calls

Scoped tool access for ROI, evals, ontology extraction, handoff checks and reporting.

OPS

Usage controls

Rate limits, audit logs, dashboards, billing events and anomaly visibility.

EXECUTIVE

FDE workflows

Board-ready summaries, scoping review, portfolio status and productization signals.

Readiness checklist

What must be true before any production claim.

RequirementBar to clear
PersistencePostgres-backed durable tenant state
Rate limitsRedis-backed controls, not process memory
BillingSigned, idempotent webhooks, tested end-to-end
AuthTenant-aware authorization and strict CORS
MonitoringStructured logs, metrics, alerts, error tracking
Load testsReal pass/fail under realistic concurrency
Governance & access

Least privilege by default.

Governance model
Narrow business actions
MCP tools expose scoped business actions, not universal shell power. Resources are scoped to tenant and workflow; human review stays required for high-impact or irreversible actions.
Waitlist
Join when it's ready for serious beta use
Install the Skill first. If your team needs shared context, governance and hosted workflows, request access.
Request on GitHub →