OMA MCP tools for Lamoi WaaS (staff and customer)

FeatureOpenView on roadmap· 14 days ago

Imported from GitHub issue El-SaMa/oma#173 by @El-SaMa.

Goal

TEKORI, staff and customers' own AI agents reach the connector only through OMA MCP tools. Follows the rules: extend the admin MCP properly; a product is done when staff and customer MCP fully cover it.

Tasks

Staff tools oma.admin_waas_*: list sites, site detail, provision, suspend, unsuspend, delete (confirm), any connector op on any site, audit log, snapshots, undo.
Customer tools oma.waas_*: the same ops on the caller's own sites only, scopes by plan.
Every write returns a proposal + confirmToken, applied with oma.confirm_tool; destructive ops also mint the connector's human confirm token.
Token minting: OMA signs connector tokens per call (short-lived, scoped, actor = staff user, customer user or tekori:<job>).
TEKORI's service identity: a scoped key that can only act on sites linked to the TEKORI job's organisation.
Handbook page (staff) + lines in the customer docs; live MCP check of every tool before calling it done.

Acceptance criteria

Tests: customer cannot touch another org's site; TEKORI key cannot touch a site outside its job's org; confirm flow required for writes.

Depends on

El-SaMa/lamoi-waas#15, El-SaMa/lamoi-waas#16.

Plan key W18. Epic: El-SaMa/lamoi-waas#25.

Comments (0)

No comments yet.

Join the discussion