MCP Bêta / Governance

Hosted MCP comes after open-source trust.

The Skill is usable today. MCP Bêta is the planned hosted layer for team context, governed tool calls, usage controls, dashboards, and Executive FDE workflows. It is intentionally not presented as production-ready.

Install SkillRead readiness article
mcp-beta.yaml
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
  - idempotent Stripe webhooks
  - strict auth + CORS
  - monitoring + load tests
Positioning

MCP is the execution layer, not the launch product.

FDE Consultants Protocoles earns trust through the local Skill, Docs, Academy, and market intelligence. The hosted MCP layer should only add value where teams need shared context, governed tools, auditability, and collaboration.

What MCP adds

Planned hosted capabilities.

These are directionally planned capabilities, not a production guarantee.

Context

Team RAG

Tenant-aware retrieval for 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 production claims.

PersistencePostgres-backed durable tenant state.
Rate limitsRedis-backed controls, not process memory.
BillingStripe webhooks idempotent and tested.
AuthTenant-aware authorization and strict CORS.
MonitoringStructured logs, metrics, alerts, and error tracking.
Load testsNon-fake pass/fail under realistic concurrency.
Governance model

Least privilege by default.

MCP tools should expose narrow business actions, not universal shell power. Resources should be scoped to tenant and workflow. Human review should remain required for high-impact or irreversible actions.

Waitlist

Join when the hosted layer is ready for serious beta use.

Install the Skill first. If your team needs shared context, governance, and hosted workflows, use the Bêta request path.

Request beta access on GitHub →